New version pending for publication #
For every new Traveler App version, ZF will provide the customer with:
- The new app version via tester access
- The release notes in English (new features and bug fixes)
The customer can then decide when the app will be made available to the travelers in the Google or Apple stores.
Tester access to the new version #
Android (via Internal testing track) #
Prerequisites #
- Customer provides Google account (email address).
- ZF adds the Google account to the user list of app testers.
- ZF provides the URL of the test track to download the app.
- Customer accepts to become a tester.
Procedure #
- Go to the URL.
- Confirm to be using the same google account that was granted access to the test track.
- Tap download it on Google Play.
- On the store page, tap Installed.
iOS (via TestFlight) #
Prerequisites #
- Customer provides Apple ID (email address).
- ZF sends the invitation email for store access.
- Customer accepts the invitation.
- ZF sends invitation email for app tester access.
- Customer installs the TestFlight app and can view the Traveler App in it.
Procedure #
- Use the mobile device associated with the Apple ID provided for test access.
- Open the TestFlight app.
- Tap Update to install the new version.
Submission for review #
The publication of apps is managed using the following interfaces.
- Android: Google Play Console
- iOS: App Store Connect
Proceed with the steps below to submit a new version. Once submitted, Google needs about 24 hours and Apple needs about 48 hours to review it (business days). If for any reasons the new version is rejected, another submission is needed which will take an additional 24-48 hours.
Android #
- Access the app in Google Play Console.
- Verify how the publication will proceed after approval (manual or automatic), see section below.
- On the left panel, select Release > Production.
- In the upper-right corner, click Create new release.
- In section App bundles and APKs, click Add from library. Select the most recent available version. Click Add to release.
- Click on Next.
- In section Release details, under Release notes, click on Add release notes. Replace the “Enter or paste…” with your release notes for each language. Ensure to keep the text enclosed with “<en-US>” and “</en-US>”.
- Click Save, then Next, and Save.
- In the lower-right corner, click Review release.
- Ignore yellow warnings, and in the lower-right corner, click Start rollout to Production.
- On the left panel, select Publishing overview, and click on the button Send 1 change for review.
- Wait for the review.
iOS #
- Access the app in App Store Connect.
- On the left panel, next to iOS App, click the + button. Name the new release with X.X.X as it will be changed later.
- On the left, select X.X.X Prepare for Submission, scroll down to What’s New in This Version, add the release notes. Save the modifications.
- On the right, switch to another supported language and repeat for all localized.
- In the same page, scroll down to the section Build, click Select a build before you submit your app. Select the most recent available version.
- In the same page, scroll down and verify how the publication will proceed after approval (manual or automatic), see section below.
- In the upper-right corner, click on Save, and on Add for review.
- After submission, click on Submit to App Review.
- Wait for the review.
Availability on stores after approval #
Publication after approval (manual VS automatic) #
Once the review is approved, it is possible to decide whether new app versions are automatically released on the stores after being approved, or if the release manager has to press a button. This can be useful if for instance, there is a specific communication around the new version release for the travelers.
Note that if the publication is planned or manual, it can take up to 4 hours to be downloadable from the moment the publication is triggered.
The default configuration is that updates are published automatically as soon as they are approved. Proceed as below to switch to a controlled publication for each future update (this can be reverted anytime).
Android #
- Access the app in Google Play Console.
- On the left panel, select Publishing overview.
- In section Managed publishing status, click Manage.
- Select Managed publishing on, and click Save.Submit the updates for review.
iOS #
- Access the app in App Store Connect.
- On the left panel, select Prepare for Submission for an existing new release preparation, or first create a submission.
- Scroll down to the section Version Release.
- Select another option than Automatically release this version.
- In the upper-right corner, click Save.
- Submit the updates for review.
Manual publication to stores #
Once the review is approved, manually publish the new version.
Android #
- Access the app in Google Play Console.
- The Dashboard view should show the status Ready to publish.
- Click on Go to Publishing overview, then on the button Publish x change(s). Note that all changes ready to published are published together, it is not possible to publish one by one.
iOS #
- Access the app in App Store Connect.
- On the panel, the status should be Pending Developer Release with a yellow icon.
- Select the new version.
- In the upper-right corner, click on Release This Version.
Published status #
Once the review is approved and published, verify the status as follows.
Android #
- Access the app in Google Play Console.
- On the left panel, select Release > Production.
- Select the tab Releases.
- The status should be Available on Google Play.
iOS #
- Access the app in App Store Connect.
- On the left panel, under iOS App, the status should be Ready for Sale.
- If you see the previous version, reload the page and it disappears.