Lots and lots of folks have been expressing concerns, posting questions, and running into small gotchas when working with the BT core code and iOS 6 (combined with the latest version of Xcode). We've been working hard at adjusting, improving, and preparing future app source code downloads for iOS 6 and this post is designed to give you an idea of what we've been doing and what still needs done (on our end). This is related to buzztouch v2.0 only, v1.5 and v1.4 are unaffected. What we have already done (you may notice these changes in your source code downloads): --Default launch images in Xcode have changed. We changed the default images in your core project. The default images are 100% black now, no text on the images. Some of the previous sizes are no no longer included in the download (unnecessary) and some new ones are included. You'll notice [email protected] and Icon_144.png are now included in the download. --App Icon: The newest packages include the Icon_144.png file. HOWEVER, the icon upload screen is still asking you to crop your upload to 72 x 72. Expect this to change soon. When it does, expect the "cropper" to ask you to select a 144 x 144 area for the icon. Until then, you're Icon_144.png file will be of LOW QUALITY because our backend is scaling UP the 72 x 72 image to 144 x 144, making it blurry. You can change this in Xcode after you download your project. When we finish altering the icon upload screen the "blurryness" (word?) should go away. --Compiler Warnings: "setStatusBarHidden:animated" deprecated warnings should no longer appear in your project downloads. This was an issue with some of the core files. There are still some compiler warnings in some of the code in some of the plugin packages and we have NOT updated those yet. We will. --Compiler Errors: Recent projects, when compiled with the latest SDK for iOS 6. were showing errors like: "Semantic Issue: Use of undeclared identifier 'ADBannerContentSizeIdentifiedLandscape'" These were related to how the iAd's framework was being references. Apple changed this. We've updated the core files already and you should no longer see these compiler errors. What we have NOT done yet: --Fixed the Orientation Change logic for Landscape and Portrait. This is a bit tougher than most folks realize but we will get it updated when iOS 6 is officially released. The challenge is accounting for all the plugins, accounting for older devices (and they way they work) and newer devices, and the way iOS 6 handles rotation. --Fixed compiler warnings in various plugins. These should not be too tough. --Fixed screen layout size issues in various plugins. We need to go through each plugin and make sure there are no references to "320 x 480" screens when the device is a iPhone 5. This should be easy but could be tough. It too is related to the plugin updates we'll be rolling out soon. Feel free to post to this thread if there are other issues you're aware of that we have not identified in this list. It's generally a free-for-all for a few weeks as some folks begin to use the newest SDK and simulators and devices while others stick with the old stuff. It will iron itself out eventually. This process took about 2 weeks when all said-and-done when iOS 4 came out. There is no reason to believe iOS 6 will take us longer to "catch up to." It's cold in the boat tonight.

Thanks David - Will we need to upgrade to a later control panel?

Not at this point. We have been working on an update to the self hosted control panel but it won't be ready for awhile. It's not related to all of this. The download server on our end is handling all these changes so all should be well as we move through the iOS 6 update. When we begin to roll out plugin updates (to the ones that need it), you'll want to update those on your self hosted server. This is a different idea than the self hosted package itself.

Hi David, thanks for the updates. The only big problem I've seen (at least for me its big) is the fact the in IOS 6 the apps with map locations screen when getting driving directions it does not open the new native map app, it opens google maps on safari. When you say these new changes will occur when we download a new package, you're refering to downloading from BT server control panel, not self hosted, right? Thanks. Cheers. Miguel

@David, saw you're answer for the maps question in the other thread. https://www.buzztouch.com/forum/thread.php?fid=2005CEF88177E55F07444E1&tid=2005CEF88177E55F07444E1 Thanks

@MadRod: The changes we implement will show up in your self hosted downloads too. Remember, the Core Project files come from us so we can keep you updated with the latest stuff. This means that when the buzztouch.com downloads are updated, your self hosted downloads will be too. However, keep in mind the relationship between the plugins on your server and the core project files on our server. When we get to updating plugins, you'll need to update those on your server. You click "download"... a) Your self hosted control panel contacts our server. b) Our server delivers an application package to the self hosted panel. This package is the "latest" we have with all the core updates we make from time to time. c) The self hosted panel adds all the plugins you have installed on your self hosted control panel into your project. d) You download the final package from your self hosted server.

Understood. Thank you. Miguel.

Thanks for the update!

Thanks for the updates!!

Thank-you !

Thank you David, There is still this Error (Don't know if anyone else is getting this): http://gyazo.com/b4061d00236bb0914b78d40bcecccab1 This is on Xcode 4.5 Thank you, Raoul

Yes, David mention this error in his first statement in this thread. Miguel

Oh, very sorry, I missed that. Thanks again!

Great updates, thanks David. After installing the iOS 6 xcode update yesterday I was wondering what to do with my projects that would no longer compile :) Problem solved. Project compiled and ran with no errors, so now I can get back to the app submission fixes on an iOS tested version. Keep up the great work and stay warm on the boat!

Thanks for the update David :) One point of clarification... I have an app that is on v1.5 and has a ton of traffic, etc. Do I need to update my app to v2.0 in order to able to not have errors in iOS 6 & support the iPhone 5 screen size? You mentioned that "This is related to buzztouch v2.0 only, v1.5 and v1.4 are unaffected." I'm not sure what that means. I'm having some of the Xcode errors you mentioned when I compile. If I don't have to update to v2.0 (how do you do that?) than that would be awesome. Thanks for all your hard work and help!

@ryanmaher777: Yes, no, yes, no, confusing I realize. Here's the thing, and it's a bit of a bummer but nothing is impossible. If you don't do anything to your app, and leave it in the market, it will run on iOS 6 / iPhone 5. Or so they say. This means you wont' have to re-compile or re-submit anything and therefore will not see any of these compiler issues I'm referring to. But, if you want to update you app, make some improvements, etc, you'll need to re-compile. When you re-compile with whatever changes you'll end up making, you'll have to isolate some syntax issues and errors. Most of these are listed in this thread but more may surface. None of them will be tough to fix but it will take a little patience trying sleuth them out. Again, most of them are mentioned in the top of this thread. If you're planning to do an update, you may consider re-creating your app using v2.0. This may or may not be time consuming, I have no idea how "heavy" your app is and how many screens you'll need to re-create. This would save you from having to fix anything (we'll have them fixed) but for sure it's a trade off. In either case, the forum will help you get this ironed out when the time comes.

Hi there, I have a problem with ads and IOS 6.0. When I compile to target device 5.1 ads display correctly, iphone and ipad. When I compile for IOS 6 target, ads appear for a second and then disappear. The compiler says that there is a network problem. Any clues? Thank you.

@Marko73 The code has not been updated for 1.5 yet, only 2.0 I don't want to speak for him... But, David is probably working on this. Hope this helps, Raoul

Maps on IOS 6 seem to behave differently when opening for driving directions. My app shows own location and has a destination pin with the option to open the native maps application to route directions, If I click OK, I used to get a map in an app showing the route. With IOS 6 I get google maps opening in a browser and going to the step by step directions. Is this correct/expected behaviour?. Is this likely to change in the future - ie will BT support the local map app?

@AlanMac: Yup, iOS maps behave different with iOS 6. Apple has not explained this change in behavior and we hope they do soon. We're hoping the update we release for the maps plugin has some added features to support what we don't know about yet! LOL. You've probably heard all the grumbling in the news about iOS 6 not using google maps and how folks are frustrated. It's all related I'm afraid. We're not doing any change to the maps plugin until we understand (all developers are waiting) what can / can't be done with the new maps logic in iOS

Hi David :) Can i just do the changes manually instead of re-downloading the source code from buzztouch? Do you think it's easier that way if my app has tons of manual code (socialize, appoxee, etc)? nevermind, tried it and i think it's easier to re-download lol