Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: document release certificate generation process #1279

Merged
merged 2 commits into from
Sep 27, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 29 additions & 2 deletions IOS_RELEASE.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,30 @@
## Distribution Certificates

Most of the time the build is created by running the release action with no issues. If this is the case you can skip to the next section.

If an IOS build has failed, this may be because of an expired distribution certificate from Apple.
When this happens, you should do the following:

**Step 1**

Visit https://developer.apple.com/account/ios/certificate/ and generate an Apple Distribution Certificate for Apple Distribution

![Distribution Certificate](docs/images/ios_certificate.png)

and a Provisioning Profile for App Store Distribution.

![Provisioning Profile](docs/images/ios_provisioning_profile.png)

**Step 2**

Update the certificates on the expo dashboard. To do this you should select the optic project, and select Credentials -> iOS -> com.nearform.optic. On this screen, you will be able to upload the newly generated Distribution Certificate and Provisioning Profile.

![Expo Dashboard](docs/images/expo_dashboard.png)

**Step 3**

Once the new credentials have been uploaded, you can re-run the failed build action, and follow the steps below.

## Submitting for review

Once a build is available to the AppStore Connect and has finished processing (usually takes about 10-15 minutes from the time Expo shares the build), you can proceed to create the new version on the platform.
Expand Down Expand Up @@ -60,10 +87,10 @@ Finally press “Add for Review” at the top right corner. Now it’s the Apple

![Step 1](docs/images/ios_release_store_step_1.png)

If you selected “Automatically release this version” during the submission process, you don’t have to do anything else. Once the app is approved, it will show up in the stores in the next few hours - it does takes some time for the store to make it available to everyone.
If you selected “Automatically release this version” during the submission process, you don’t have to do anything else. Once the app is approved, it will show up in the stores in the next few hours - it does takes some time for the store to make it available to everyone.

**Step 2**

![Step 2](docs/images/ios_release_store_step_2.png)

If you’ve selected to “Manually releases this version”, then the app will be at a “Pending Developer Release” state, meaning you will have to log in and press the button that says “Make App Available”, on the top right corner.
If you’ve selected to “Manually releases this version”, then the app will be at a “Pending Developer Release” state, meaning you will have to log in and press the button that says “Make App Available”, on the top right corner.
Binary file added docs/images/expo_dashboard.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/ios_certificate.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added docs/images/ios_provisioning_profile.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading