Does the "DO NOT APPROVE" method apply also for updated app versions? Is it downloadable only by the publisher?
I asked a similar/related question yesterday at the developer summit. The app store team told me that once an app is approved that any updates are basically available to users immediately. So, in answer to your question, if you want to test an update (or hold the update back for some reason), you would need to create a second app.
In your case, all the installed users of your BC-1000 app are now going to be notified of an update to your app.
Ok, thanks.
Using Fit Contribution, testing can be done effectively only by uploading the app to the store to see the results in GC.
So if you find problems afterwards it' hard to hold back.
I may give the app another title!?
You don't need to give it a different title.. you need to use a unique uuid in the manifest for the test app. Of course using a different name will help to differentiate between them, but it isn't necessary as far as I remember.
As mentioned, this topic was discussed in one of the breakouts.
We have a beta-app feature that we'll be adding to the store in the future that will allow you to upload a second version of an app to the store for testing that will not be exposed externally. I also had a discussion with the store team about allowing developers to white list a group of beta testers that would have external access to beta apps. We know the "DO NOT APPROVE" thing is a little janky right now, but there are definitely things in motion to address this particular shortcoming. A basic ability to upload beta apps is at the top of the store team's to-do list, so I expect to see that added before the end of the year.
