Skip to content

Commit bdf529a

Browse files
authored
Merge pull request #873 from marionbarker/working-docs
Update some Browser Build Information
2 parents 2514a59 + e1f4509 commit bdf529a

File tree

5 files changed

+42
-3
lines changed

5 files changed

+42
-3
lines changed

docs/browser/build-dev-browser.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,3 +141,27 @@ Your default branch has been changed.
141141
The automatic update and build features are available for both the released (`main`) and development (`dev`) branch, but only for your default branch. For any other branch name set as your default branch, there is no automatic update available but the automatic build will run monthly.
142142

143143
Be sure to read this page: [Automatic Update & Build](automatic.md){: target="_blank" }.
144+
145+
## What Happens in TestFlight
146+
147+
As soon as you build one version of the app from the `dev` branch, that version number (which is higher than the `main` branch) will show up at the top of the available builds in TestFlight.
148+
149+
Suppose you then return to using the `main` branch after your excursion to the `dev` branch.
150+
151+
> *For this example, version 3.4.4 is the released version from the `main` branch and version 3.5.0 is the development version you evaluated.*
152+
153+
Every time you open TestFlight on your phone and select the *Loop* app, it will offer the most recent 3.5.0 version to be installed if you just tap **Install**. You might be in a situation where that build is about to expire or you decide you don't want to test this on your looping phone. In some cases, the released version, 3.4.4, might have fixes that are not available in a development branch.
154+
155+
You have your choice:
156+
157+
* You can manually go into TestFlight each time `main` is automatically built, Select Previous Builds, then choose 3.4.4 and install the top listing
158+
* You can log in at: [App Store Connect: Apps](https://appstoreconnect.apple.com/apps){: target="_blank" }
159+
* Select your *Loop* app
160+
* Click on the TestFlight tab
161+
* For each 3.5 build, click on the row for a build
162+
* Select Expire Build on upper right
163+
* This leaves only the released version, 3.4.4 for this example, available in TestFlight on your phone
164+
165+
![expire builds with higher version numbers](img/testflight-expire-dev.png){width="700"}
166+
{align="center"}
167+
58.9 KB
Loading

docs/browser/secrets.md

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,22 @@ You must be logged into your *GitHub* account before starting this step. If you
285285

286286
## Make up a Password
287287

288-
If you have not already made up a password, do it now and record it as <code>MATCH_PASSWORD</code>.
288+
If you have not already made up a password, do it now and record it as <code>MATCH_PASSWORD</code>. Note that if you [build more than one app](other-apps.md){: target="_blank" }, you use the same <code>MATCH_PASSWORD</code> for all the apps. Every app needs to have the same 6 Secrets.
289+
290+
!!! info "What is this Password used for?"
291+
The <code>MATCH_PASSWORD</code> is a special password called a *passphrase* that is used to encrypt and decrypt your certificates from *Apple* so they can be used when building with *GitHub*; it helps keeps your certificates secret and safe.
292+
293+
A *passphrase* is a little different from a regular password. A password is what you usually use to log in to a website or game. A *passphrase* is a secret code that helps protect important files by adding an extra layer of security when files are encrypted.
294+
295+
### *Passphrase* Suggestions
296+
297+
To make a *passphrase* that is hard to guess and keeps your certificates safe:
298+
299+
* Use at least 15 characters (20 is even better) and you can include spaces
300+
* Mix in big letters, small letters, numbers, and symbols like $ or #
301+
* Don’t use words or numbers that people might guess, like your name or birthday
302+
303+
If you already created a MATCH_PASSWORD that does not meet the criteria listed above, no worries, you are protecting an *Apple* developer certificate - not the family fortune. That information is provided for new builders who want guidance.
289304

290305
## Next Step
291306

docs/faqs/glossary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -210,7 +210,7 @@ When Google Translate is selected:
210210

211211
**<span translate="no">GH_PAT</span>**&nbsp; (GH_PAT): One of 6 Secrets: Generated with your GitHub account; set it to never expire
212212

213-
**<span translate="no">MATCH_PASSWORD</span>**&nbsp; (MATCH_PASSWORD): One of 6 Secrets: password you make up but must save and cannot change without deleting the Match-Secrets repository
213+
**<span translate="no">MATCH_PASSWORD</span>**&nbsp; (MATCH_PASSWORD): One of 6 Secrets: Git repo encryption passphrase, used to encrypt the Match-Secrets repository when it is created. You must save and use the same MATCH_PASSWORD for every repository if you build multiple apps.
214214

215215
**<span translate="no">SHA-1</span>**&nbsp; (SHA-1): Secure Hash Algorithm 1; used to generate an alphanumeric code for commits in git (github)
216216

includes/tooltip-list.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@
9898
*[FASTLANE_KEY_ID]: One of 6 Secrets: Key ID provided when you create an API key in App Store Connect; it is associated with the FASTLANE_KEY
9999
*[FASTLANE_KEY]: One of 6 Secrets: Really long key (several lines); it and FASTLANE_KEY_ID are generated together
100100
*[GH_PAT]: One of 6 Secrets: Generated with your GitHub account; set it to never expire
101-
*[MATCH_PASSWORD]: One of 6 Secrets: password you make up but must save and cannot change without deleting the Match-Secrets repository
101+
*[MATCH_PASSWORD]: One of 6 Secrets: Git repo encryption passphrase, used to encrypt the Match-Secrets repository when it is created. You must save and use the same MATCH_PASSWORD for every repository if you build multiple apps.
102102
*[SHA-1]: Secure Hash Algorithm 1; used to generate an alphanumeric code for commits in git (github)
103103
*[Sign Targets]: associate a Developer ID with an app; must sign all targets for a given app
104104
*[submodules]: for Loop, submodules are repositories defined in the Workspace repository that are required to build the app

0 commit comments

Comments
 (0)