Here's a question which will affect a lot of BT users: I'm submitting an app which was developed using BT 1.5 / Xcode 4.6 / Lion. In a month or two when iOS7 is released I'll have to format my mac and redevelop the app using Mavericks, Xcode 5 and BT 2 to make it compatible with iOS7, i.e. completely afresh. Does anyone know if its possible to submit a completely new app to Apple as an update to an existing app and if there is any problem with retaining existing provisioning profiles?

The 'big' thing is going to be proving to Apple you're the same person. And that shouldn't be too hard; log into iTunes connect. Generate new certificates. Heck, generate new everything. 1) You need to use the same credentials that 'owns' the app. 2) Needs to be the same 'bundle ID' as the original app. (com.something.or.other) 3) Needs to be an incremented version number (1.1+) I don't know if you can keep the current provisioning profiles; but I wouldn't worry about it. In fact "I" would just trash all of them and start from scratch. Apple has a list of the apps and bundle ID's, and yes you'll need to submit a couple of new CSR's, but it would be a clean sure way to know the certs are good. and again, if you're the same credentials, bundle Id, and incremented version, you're good. Cheers! -- Smug

Thanks Smug, Will act on your advice. I think I'll also clone my HD onto a USB drive as a back up just in case! Rohan

Actually Smug, your comment had me thinking... It should therefore be possible to create a new app under BT, release it as an update to Apple and still retain 2 apps in the BT control panel, one for legacy devices, and one for newer devices. i.e. two report to cloud configurations ?

I would publish it as a new app with the same name as before, but put a suffix of 2.0 on the name. That way, the new app is still associated with the old app. Then publish an update to the old app, change the Splash Screen to let Users know of the new 2.0 app if they have upgraded to iOS 7. -- Niraj