Hello, I may be being a bit naive here but I cant figure out how this would work, help would be much appreciated: I have an app which i haven't updated for a couple of months and it has 3,000 push subscribers (I send pushed through the buzztouch hosted panel). I am now updating the app so have created a new app on my control panel and am designing it at the moment - when ready to upload i'll change the bundle identifier to the original and send it to apple. Does this mean I will lose all of those subscribers that have said yes to push or is there a way of transferring them over? I also thought about putting the original app in design mode then sending off the update but I presume this would mess with people that have the unupdated app on their device. Hope that all makes sense Thanks

I find design mode / live mode does not work for me, for some reason the updates always go through when I make an update from my Control Panel no matter which mode I am in! As for the push notifications, my experience is that as long as you code sign the app with exactly the same apple certificates etc. that you created before, you should be fine. Not so sure about Android push, in general I find once you have it working you are OK, but the question 'do you want push' may be asked when the updated app loads for the 1st time. Alan

Brilliant, Thank you Alan!

Alan and Hugo - I wouldn't say I am sure about what Alan said. You have to remember that the APNS token is displayed in the CP when sending a notification, and it'll only send to the selected ones - just because the certificate is used doesn't mean the users will receive them... You will not be asked if you want notifications because it still has the settings for the previous build, and so they won't get registered to the new app in the CP. So, to answer the final question... My knowledge would suggest that yes, you would lose your subscribers.

Ah rubbish - thanks for your help. What would you recommend I do to update an app and keep push notification subscribers/give then a chance to subscribe again?? Cheers

Ed may be right, I am no longer as sure myself now! The complication here (I think) is that you are building a new app with a different control panel for it; on reflection I am not quite sure how BT push will behave between the old and the new versions and the two control panels. Possibly you may have to send from both panels for a while!. Again, I am not sure, I have faced this scenario using Parse push and I think my advice would have been OK on Parse push. I think if you were to build all the additional plug-ins, screens etc. into your original app (not the copy) and publish that, but keep the functionality the same for now, then roll out the new features that taking advantage of the new plug-ins after apple have published and people have upgraded, you could may be able to keep everything on the same control panel and avoid the complications. Alan

My only thought here is to use a different App ID, as it would ask the user to subscribe to that one, not the old one.

Okay cool - I was under the impression you had to keep the original apple id whenever you updated an app. Is that not the case? Cheers

If the user deletes the app and installs it again, whether the same build or a newer build, they get asked again to register for push notifications. If they leave the app in place, and a newer build gets installed as an update then -- I believe -- their prior registration holds.