Building and submitting an update to your iOS app is much easier than creating it for the first time. The following is a step-by-step guide to the process.
If you are creating a new Mag+ app to overwrite an existing app created in another platform, you normally cannot use a Push Notification to send a message to users of the older app. The Push Notification would only go to users of the new Mag+ app. Your new app may, however, qualify for a Transfer, which does allow you to send a Push Notification to users of the old app. This would allow you to inform them of your update. For more information and eligibility requirements, read the Apple article "Transferring and Deleting Apps."
You cannot, unfortunately, use the "Transfer App" feature if your older app offered free subscriptions and your new app requires paid subscriptions.
How to Update Your iOS App in the Apple App Store
2. Change your Build Options or Customizations as needed.
Each section of the Assets and Configuration area features a label indicating whether all the required information has been completed. If an area requires more configuration, or if a validity check fails, then the section will read "Incomplete" and you will not be allowed to create a new build.
3. Once all fields have a "Complete" label, you can click the "Generate New Build" button at the bottom of the screen.
4. In a few minutes, you can reload the page and see a new time-stamped link to a package containing your app file.
The ".tgz" link downloads a package of files to your computer. Inside is a "AppStore_x.x.ipa" file that you can upload to iTunes Connect for submission to the Apple App Store.
Note: There is also a "Send e-mail" link that generates an email you can send to anyone who has a device saved on your ad hoc certificate. Those users can then click on this link from their iOS device (or paste it into Safari on their iOS device) and it will download and install the test version of the app.
5. Test your updated app before submitting it to Apple.
In the ".tgz" package is an "Adhoc_x.x.ipa" file you can drag to your iTunes application to install it on your iOS devices for testing. You can also read more about testing your app in the article "iOS - How to Install Your Test App."
8. In the window that appears, enter the new version number of your app and click on "Create."
Note: This version number is the version of your app displayed in the Apple Store. It is not the Mag+ version number.
9. Review the metadata in the new version and make any changes to screenshots, description, etc.
Note: Any changes you make will only get published when the new version goes live. Your current copy and metadata will remain the same until then.
10. Upload your new build using Application Loader.
Please refer to our Uploading Builds Using Application Loader article for reference.
The "AppStore_x.x.ipa" file to upload is located within the ".tgz" file you downloaded from the Mag+ Publish portal.
Note: Do not submit the file labeled "dSYM", only the "AppStore_x.x.ipa".
11. When submitted, the build will go through a "Processing" stage to check for errors.
This status of your upload is visible in the "Prerelease" tab on the App Summary page. When this stage is complete, you will be able to select the build as a new version of your app.
14. Now click on the "Save" button in the upper right-hand corner of the screen.
This will save your build selection for the current version.
16. Click on "Submit for Review" and answer Apple's final questions about your app and then click on "Submit."
For more information on what to check for "Advertising Identifier" information, refer to the "Notifying Apple of Advertising Identifier (IDFA)" section of the article "iOS - Adding Third-Party Integrations."
17. After a successful submission, your status will change to "Waiting for Review."
Note: At this point you cannot make any changes to the metadata until after the app is approved.
Updates take about as long to approve as new submissions, so you must wait for Apple to approve the submission. If you are updating your app to fix a critical bug, you can request an expedited review, but use this only for emergencies.