Skip to content
This repository has been archived by the owner on May 23, 2023. It is now read-only.

Latest commit

 

History

History
87 lines (51 loc) · 5.17 KB

ios-distribution-guidelines.md

File metadata and controls

87 lines (51 loc) · 5.17 KB
Raw

iOS Distribution Guidelines

Testflight

Steps to walk a new internal tester through setting up TestFlight for beta app distribution.

1. Apple ID

In order to be added as a Tester, please send your Apple ID to rabin.joshi@nrccua.org asking to be added to iTunes Connect team. If you do not know your Apple ID you can find it from Settings > iTunes & App Store. If you're not signed in, or are signed in to a different account, please make sure that you are, and to the same account that you've mentioned in the email.

Settings > iTunes & App Store 1 Settings > iTunes & App Store 2

Please ensure that the email is a primary email for the Apple ID, with associated birthdate and the recovery emails. If this is not the case the folowing message is displayed when I attempt to add a new user:

This email address is not available for use as an Apple ID. You may already have an Apple ID associated with this address. Please try again or sign in using your existing Apple ID.

2. iTunes Connect

  • You will recieve an invite from iTunes Connect with the subject Welcome new iTunes Connect User. Please tap Activate your account.

  • That'll launch Safari and display the iTunes Connect Terms of Service.

  • On tapping Accept. You'll be taken to Sign In Screen. Please verify that you can successfully Sign In.

Welcome new iTunes Connect User Terms of Service

3. TestFlight

  • Install the TestFlight App from the App Store. You can find it by following [this link] (https://itunes.apple.com/us/app/testflight/id899247664?mt=8) or by searching for ‘testflight’ in the App Store.

  • Lauch TestFlight and accept the Terms & Conditions.

  • Select Allow Push Notifications. Doing this will ensure that you’ll receive notifications every time a new version on the app is pushed.

testflight TestFlight Terms and Conditions Allow Push Notifications

4. Wait!
  • Once you've completed all the steps above you're all set to recieve builds whenever a new one is posted.
5. Installation
  • When a new build is posted, you’ll receive an email notifying you of the new version of the app being available. You must open the email on your device.

- Tap `Start Testing` and `Accept` and `Install`.

- The App will be downloaded with an orange mark next to its name to indicate a test build.
6. Subsequent Builds

From this point on, whenever a new build is pushed to TestFlight you'll recieve an email (in addition to the push notification if you’ve chosen to receive them) like before. All you need to do now is Update your app and you'll have the latest version up and running.

Versioning

Apple specifies the following rules for valid version and build numbers in Technical Note TN2420:

  • The value for a version number or build number must consist only of '.'s and numbers and must begin and end with a number.
  • Each integer value separated by a period is a component of the version. Version numbers and build numbers may have up to three components separated by periods.
  • The total number of characters in your version number or in your build number cannot exceed eighteen characters.`

Apple doesn't define or require a specific convention for what eacr of the components in the version/build numbers are supposed to signify. In keeping with semantic versioning, here's what we do:

  • Every new release will have a unique version number
  • Versions numbers will be of the form MAJOR.MINOR.PATCH
  • Significant and major releases will increment MAJOR
  • Smaller releases introducing new features and UI changes will increment MINOR
  • Bug Fixes and non-visual changes will increment PATCH

App Store Deployment Workflow

  1. Complete all feature development assigned to the version to be deployed in the dev environment.
  2. Post a release candidate (RC) build that points to the prod environment.
  3. Carry out thorough regression testing to ensire all features perform as expected. If bugs discovered, log them to the bug bucket.
  4. Determine if non-fatal bugs need to be addressed in the current release. If yes, address them and start over from Step 2. Otherwise, assign them to the next minor version and add to backlog.
  5. Obtain What's New Text
  6. Obtain App Screenshots
  7. Create a new version in App Store Connect. Enter app metadata.
  8. Choose the build to submit. Review pricing and availability. Submit your app for review.
  9. Track app status and resolve review issues if any.