The problem, as you might expect, is the app review process.
In order to get Apple to review an app update, it has to be pointing at my production server. In order for that to work, I must update the build on my production server. But of course I don’t want to do that until the app update is available in the Apple Store.
Now this isn’t a problem if I’ve only made changes that can be deployed via hot code push … but changes that can be deployed via hot code push don’t need a new app wrapper anyway. I’m concerned about things like new node modules, or an updated meteor version.
Surely I’m not the only person to have this problem, but the most pertinent forum thread I found was this one (Push new update IOS app store).
Anybody know a great way to handle this?