Hi guys, I have upgraded to Mountain lion and had quite a few warnings when packaging the build. I fixed all of these, I just wanted to point out that setStatusBarHidden:animated is now depreciated and causing warnings when achiving. Also getDistanceFrom and locationServicesEnabled Any quick, easy fixes would be useful to all..(and me:)) Many thanks.

Haha it only shows as deprecated if your build level is iOS 4 (I think) or higher. There isn't really a quick fix, but are you using BTv1.5 or BTv2.0?

I have the same problem!

V1.5 monster. I've no idea how but they disappeared on their own, well with a bit of tinkering but no changing of the code :) The warnings when packaged can pretty much be sorted with several '%' s

Haha yep, no clue why the build comes with those @"", @"". And the @"Hello @", @"Hi". But easy fix. And the reason why they went away is likely due to you lowering your build target to 3.x or 4.x.

Yup, changing the build target does have complicated implications. We've recommended building for 3.x for a long time. When you do this you should get NO errors or warnings. When iOS 6 comes out we may re-visit this idea and begin recommending 4.x or higher. If this is the case, we'll need to modify some base code to prevent some compiler warnings. "no clue why the build comes with those @"" Not totally sure what you're asking but I'll try to explain some technical stuff. In Objective C, string objects (words, sentences, etc) are created like this: NSString *myString = @"this is my string"; See the 'at' sign, this is required. There are other ways to create a string object but that's the most common. An empty, blank string is... NSString *myString = @""; So far so good. In many parts of the project you'll see method calls that take a few arguments. Oftentimes these arguments are string objects. And, oftentimes these arguments require a string. The trouble is, sometimes a string is not available when the method is called. In these cases, you could see something like... NSString *myString = @"this is my string"; [self.myRandomFunction myString] OR... [self.myRandomFunction @""]; Notice that in the first method call we passed in a string object named myString. In the second case we didn't have a variable to pass so we just passed in an empty string. In Xcode when targeting 4.x or higher, the compiler doesn't like "empty strings" that are not explicitly created before use, this causes compiler warnings. If this... [self.myRandomFunction @""]; caused a compiler warning you could do... NSString *myString = @""; [self.myRandomFunction myString]; See the difference? You're explicitly telling the compiler... "Hey, I have this string object, it's called myString and it's empty. Use it in this method call that requires a string" Hope that helps explain a bit of how Objective C and the Xcode Compiler work together to try to HELP the developer understand what's happening. Remember, warnings are GOOD, they help you discover new things, learn a bit, and see into the inner workings of iOS. Nerdy, totally. Cool. Some think so. LOL

the app won't let me download the source code when i try to download the source code from buzztouch it shows: done<div style='border:1px solid red;padding:10px;margin: 10px;backround-color:#FFFFFF;'>Oops, an error occured trying to access a resource.<div>

@MANN "the app wont' let me download the source code" What won't let you download source code? What app? How is this related to this post, "Depreciation warnings" I'm confused.

David, thanks for all the above relating to the depreciations. I have managed to successfully code a few apps prior to finding buzztouch but were many soundboards using the very simple ibaction. I also appreciate your comments with regards to warnings helping with understanding code. I enjoyed sorting the warnings when the package contents were downloaded just needed a bit of a steer with the depreciations. All the best.

when i try to download the source code from buzztouch it shows: done<div style='border:1px solid red;padding:10px;margin: 10px;backround-color:#FFFFFF;'>Oops, an error occured trying to access a resource.<div>

Yeah I've gotten that too, I believe it might be a bug.

thats nice too know it is my first app so i though it was my computer

Check out this thread and see if it helps. It's likely due to your application icon: http://www.buzztouch.com/forum/thread.php?tid=87AA7B142869E21E2898E1A&fid=2C1C22C1EADEDB22F61C5E5 Mark

thank you so much