Ad Hoc Distribution - does it update an existing pre-installed version of the app?
What happens when a user installs a custom distribution of an existing application? And what happens if this app (or a newer one) makes it to the App Store officially?
Summarizing:
- User already has v1.0 and gets dedicated hosting v2.0
- The user has ad hoc v2.0, and the v2.0 official publication hits the store.
- The user has ad hoc v2.0, and the v3.0 official publication hits the store.
In other words,
is this a special version of the standalone assembly or is it actually updating the previous version as expected from the update? And will it be updated as soon as the new version hits the store?
source to share
What happens when a user installs a custom distribution of an existing application?
I have no answer to this; I would assume it is being overwritten.
And what happens if this app (or a newer one) makes it to the App Store officially?
Nothing happens when the app gets to the app store in its own way (for example, without being notified of an update via App Store.app); however, if the user installs an App Store distribution. the previous version of Ad Hoc is leaving. I did this with an app without local storage, so I'm not sure if any local files will be saved (for example, if the app saves content as a sandboxed file).
My disclaimer: I did this before SDK3.0. I had ad hoc beta testers that I collected via email. Then several testers received the official release via promo codes.
Hope it helps.
-Scott H
source to share
Even if the distributed application is completely the same, for example the same executable file, since both are different, each version must have a different version number. So if you released 2.0 ad hoc and then released the official version, that version should be different, like 2.0.1, for organizational and clear purposes. You will find out if the client is from version 2.0, which is a special version, and if version 2.0.1 is the official version, without further information. Thus, each individual release must have a distinct and unique version number.
source to share