Frontend

Frontend-specific fixes and answers

Builds

How do I trigger a mobile build?

For most projects, a build can be triggered straight from GitHub. Go to the repository, then Actions, and select Release & Build on the left.

Use the "Run Workflow" button, put in an optional message, select the correct branch and press "Run Workflow".

To release a Beta version of the app, select the staging branch. To release changes that are currently on staging to production, use the master branch. The behaviour of the workflow changes depending on the branch selected:

• Staging: Creates a new prerelease version, updates iOS & Android versions, generates changelog, starts Staging track build

• Master: Pulls changes on staging onto master branch, creates a new full release version, updates iOS & Android versions, generates changelog, starts Production track build

For projects without a Release & Build workflow, perform the above manually. Builds can then be triggered directly through Bitrise.

How can I release a new build to TestFlight?

Once a build has completed in Bitrise, it will automatically be pushed to App Store Connect and Google Play (where applicable).

For most projects, changes pushed to App Store Connect will automatically be rolled out to internal testers. Make sure to copy any changes from the changelog into the "What's changed" section. For any projects without automated release, you'll need to select the latest version in the TestFlight section of ASC and fill out the export compliance form.

For projects using Google Play, you will need to release a new build for internal testing manually. Select Releases on the left panel, and select the new build. From here, you can paste in the changelog, and keep pressing Next until the build is released. This will slowly roll out to all users.

For projects using APKs directly, the link will be sent to the Slack channel. It can also be found in the build artefacts on Bitrise.

What's the process for releasing a new version to the App Store?

1. During development, all builds should be done from the staging branch to release to the Beta track (this is done through daily automatic builds for some projects)

2. Once signed off by clients and testers, the build can be promoted to production

3. Run the Release & Build workflow on the master branch

4. Once built, go to App Store Connect (ASC)

5. From here, confirm the build is working via an Internal TestFlight release

6. Create a new version in ASC

7. Select the build for that version

8. Update any ASC details

9. Set the changelog using the autogenerated changelog found in the repo (format nicely under the final version number, removing any irrelevant comments)

10. Add the version for review

11. Submit for review, ensuring you have set reachable contact details for the reviewer and they have a working account