I hope these non-fatal errors don't get me rejected by the App Store. On the other hand, since all of these commands have been deprecated, what am I missing out on, that the author thought I should have? http://10kapps.com/deprecations.png

Worry not. Just Apples way of saying there is a new/different way of saying that now. It will not affect App Store. Apple don't crack open your app, if it runs it runs.

True... but what was the author (of BT 3.0) hoping to do with those commands, that are now deprecated? And if Xcode can suggest the new, current, usage, the "use" hints, why hasn't 3.0 been updated?

We'll, logically Buzztouch has kept old parameters around in the source code to keep support with older Xcode versions and I bet some items are specifically for pre-iOS7 apps. I wouldn't worry too much about warnings (they don't make any difference, unless you are the developer of the code). -Cake

I would think the Control Panel preparing and exporting v 3.0, wouldn't be about iOS 5 and 6 code. I would think someone specifically wanting code for 5 or 6, would pick v 2.0. I just want to make sure we 3.0 folks aren't missing out on any features, that are no longer being called by those deprecated commands, and that are now being called by new commands - including the suggested commands in the Xcode error screen.

Buzztouch 3.0 was built during iOS 6 and 7. If you look in the BT Control Panel, there is no longer any 2.0 download option. I mention this not to make you wrong, but to hopefully explain why Buzztouch may contain some older code. Now you probably want to fix some of these errors, if that is most important to you hopefully we can help. I assume you are using self hosted? If so you might want to download your project again - to check if it contains the same errors. Sometimes the builder makes mistakes, or Buzztouch changes the package you downloaded, so it is very important to check occasionally for updates. When I get a chance I will download a project to see if it still contains these same warnings. Hope for the best! -Cake

Mine were today, and Thursday.

Alright Nick, I downloaded a new project, (today) from Buzztouch.com and the only errors I have are in (old) plugins. http://bit.buzztouch.me/previews/3d1486c7b261c427ee09e4905625d4df.png If you would like I can take a look at your project if you PM me. -Cake

I noticed you left your list items unexpended. When you expanded, did you have some of the same ones that I did? I was just curious if I am missing out on anything because the commands (perhaps?) didn't work, because they were deprecated. And if the correct, current command would produce a better result?

Here are the errors expanded... nothing really interesting. http://bit.buzztouch.me/previews/322e3b98fa815ed1e5f651f5a59b96f6.png None of the errors you are looking at are showing up on any project.

One thing I am concerned about in my App: In the Android version, the list rows are not black with gold text as specified... they are white with gold text. The same config.txt file produces results as expected with iOS 7. I'm frantically looking for the conflict, or for what is missing! Talk about the proverbial needle in a haystack! Of course, I'm talking to you about Xcode non-fatal errors, not Eclipse. I am not sure about looking for an error log there. At some point I would be OK with asking one or more members to test my Android App.

Those arent really "errors", more of a warning that its "a new way of doing it". It might just be the way android handles it and maybe some small bugs as to why the colors are different.Ive noticed that too. You'll just have to play with it. Good thing you can change it in the control panel and see it change on the device by refreshing instead of having to redownload the package everytime. Ill test your android app. if you want,post the apk or pm it