Deploying to gh-pages from @ 9492e47 🚀

Author: marionbarker

browser/automatic/index.html

@@ -3748,16 +3748,17 @@ <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Anchor l
 <p>You still need to <strong>take these actions</strong> to ensure a recent build of the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app is available in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> for you to install on your phone when you choose:</p>
 <ul>
 <li>Keep your <em>Apple Developer</em> account up to date with agreements signed</li>
-<li><a href="../bb-update/#renew-certificate" target="_blank">Renew <abbr title="Apple certificate is used to sign your iOS or Mac apps - tied to but different from your permanent Developer ID">Certificate</abbr></a> once a year</li>
+<li>Check your <em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> action if you ever get an email saying an automatic action failed</li>
+<li>Look at your <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> app on the second of every month to make sure a new build is available for you to install when you are ready</li>
 </ul>
 <h3 id="successful-weekly-action">Successful Weekly Action<a class="headerlink" href="#successful-weekly-action" title="Anchor link to this Header on this Page">&para;</a></h3>
-<p>Normally, you will see a successful <code>build action</code> once a week. This happens at 08:00 <abbr title="Coordinated Universal Time is a time standard for civil time and time zones worldwide">UTC</abbr> every Wednesday.</p>
+<p>Normally, you will see a successful <code>build action</code> once a week. This happens every Wednesday.</p>
 <p>If there are no updates to the <code>main</code> <abbr title="version of code within a single repository or workspace repository">branch</abbr>, your actions show a very short, successful <code>build action</code> as shown in the graphic below. It only takes about a minute because the logic says - no update then skip the build. </p>
 <p><img alt="normal weekly check for updates when there are no updates" src="../img/normal-check-for-updates.png" /></p>
 <p>If there is an update, the <code>build action</code> updates your <abbr title="a copy of code in a github repository other than the original">fork</abbr> and creates a new build. </p>
 <p>In that case, you should check your favorite information site to find out what the update was and then, when you are ready, install the update using the <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> app on your phone.</p>
 <h3 id="successful-monthly-action">Successful Monthly Action<a class="headerlink" href="#successful-monthly-action" title="Anchor link to this Header on this Page">&para;</a></h3>
-<p>On the first day of every month at 06:00 <abbr title="Coordinated Universal Time is a time standard for civil time and time zones worldwide">UTC</abbr>, you will see a successful <code>build action</code>. The purpose of this build is to provide a recent version of the app in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> so you are never in a situation where you have no app on your phone.</p>
+<p>On the first day of every month, you will see a successful <code>build action</code>. The purpose of this build is to provide a recent version of the app in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> so you are never in a situation where you have no app on your phone.</p>
 <p>You start getting <a href="../../operation/features/notifications/#loop-app-expiration-notification" target="_blank">Notifications</a> when there are fewer than 20 days until expiration. When you see the warning, install the newest build from your <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> app. You do not want to get the dreaded "<abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr> Beta is not available" message on your phone. (The warnings get very agressive when close to expiration.)</p>
 <h3 id="what-are-the-alive-branches">What are the <code>alive branches</code>?<a class="headerlink" href="#what-are-the-alive-branches" title="Anchor link to this Header on this Page">&para;</a></h3>
 <p>The automatic update and build feature is embedded in the build_loop.yml code and uses the <abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr> scheduling feature to trigger actions to run automatically.</p>
@@ -3786,8 +3787,7 @@ <h4 id="automatic-creation-of-alive-branch">Automatic Creation of <code>alive br
 </ul>
 </div>
 <h2 id="automatic-certificates">Automatic Certificates<a class="headerlink" href="#automatic-certificates" title="Anchor link to this Header on this Page">&para;</a></h2>
-<p>Coming soon with <code>Loop 3.6.0</code>. </p>
-<p>Already here with <code>LoopCaregiver</code>, <code>LoopFollow</code> and some other Open-Source apps.</p>
+<p>Automatic renewal of certificates is included in <code>Loop 3.6.0</code>.</p>
 <h3 id="requirements">Requirements<a class="headerlink" href="#requirements" title="Anchor link to this Header on this Page">&para;</a></h3>
 <p>You must have the <code>ENABLE_NUKE_CERTS</code> variable set to <code>true</code> for your <em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> organization, or when using a personal account to build, add it to each <abbr title="contains project files and each file's revision history">repository</abbr>.</p>
 <ul>
@@ -3802,10 +3802,10 @@ <h3 id="requirements">Requirements<a class="headerlink" href="#requirements" tit
 <li>You need a new <code>Distribution</code> <abbr title="Apple certificate is used to sign your iOS or Mac apps - tied to but different from your permanent Developer ID">Certificate</abbr> at <em>Apple</em></li>
 <li>You need to create new signing credentials for <code>Match-Secrets</code></li>
 </ul>
-<p>For the <code>Loop</code> app, up through version 3.4.4, you must to do this <a href="../bb-update/#renew-certificate" target="_blank">Renew <abbr title="Apple certificate is used to sign your iOS or Mac apps - tied to but different from your permanent Developer ID">Certificate</abbr></a> process manually. Once version 3.6.0 is released, it will be automatic.</p>
+<p>For the <code>Loop</code> app, up through version 3.4.4, you had to do this <a href="../bb-update/#renew-certificate" target="_blank">Renew <abbr title="Apple certificate is used to sign your iOS or Mac apps - tied to but different from your permanent Developer ID">Certificate</abbr></a> process manually. Now that version 3.6.0 is released, it is automatic.</p>
 </details>
 <h3 id="automatic-certificate-renewal">Automatic <abbr title="Apple certificate is used to sign your iOS or Mac apps - tied to but different from your permanent Developer ID">Certificate</abbr> Renewal<a class="headerlink" href="#automatic-certificate-renewal" title="Anchor link to this Header on this Page">&para;</a></h3>
-<p>Some Open-Source apps, in particular <code>Trio</code>, <code>LoopCaregiver</code> and <code>LoopFollow</code> already have this capability. It will be available in with the next release of the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app (3.6.0).</p>
+<p>Some Open-Source apps, in particular <code>Trio</code>, <code>LoopCaregiver</code>, <code>LoopFollow</code> and <code>Loop</code> have automatic certificate renewal.</p>
 <ul>
 <li>
 <p>If your signing credentials for the app being built are invalid and <code>ENABLE_NUKE_CERTS</code> is <code>true</code>, then signing credentials will be cleared from your <code>Match-Secrets</code> <abbr title="contains project files and each file's revision history">repository</abbr>, a new <code>Distribution</code> certificate will be created at <em>Apple</em> and signing credentials for the current app will be generated and stored in <code>Match-Secrets</code>.</p>
@@ -3833,7 +3833,7 @@ <h3 id="open-source-app-schedule">Open-Source App Schedule<a class="headerlink"
 <tbody>
 <tr>
 <td style="text-align: left;"><span translate="no"><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></span></td>
-<td style="text-align: center;"><code>dev</code> only</td>
+<td style="text-align: center;">&#x2705;</td>
 <td style="text-align: center;">09:00</td>
 <td style="text-align: center;">07:00</td>
 </tr>
@@ -3869,7 +3869,7 @@ <h3 id="open-source-app-schedule">Open-Source App Schedule<a class="headerlink"
 </tr>
 <tr>
 <td style="text-align: left;"><span translate="no">xDrip4iOS</span></td>
-<td style="text-align: center;">n</td>
+<td style="text-align: center;">&#x274C;</td>
 <td style="text-align: center;">16:00</td>
 <td style="text-align: center;">14:00</td>
 </tr>

browser/bb-errors/index.html

@@ -4180,7 +4180,7 @@ <h2 id="help-with-errors">Help with Errors<a class="headerlink" href="#help-with
 <div class="admonition important">
 <p class="admonition-title">Get Help, Not Frustrated</p>
 <p>For first-time builders, there are a lot of one-time steps that all have to be correct and many screens look similar.</p>
-<p>If you are updating your build or renewing certificates, the process can be confusing and some error messages can be misleading.</p>
+<p>If you are updating your build, the process can be confusing and some error messages can be misleading.</p>
 <p>If you are having trouble, don't hesitate to ask for help.</p>
 <p>Please do NOT:</p>
 <ul>
@@ -4234,7 +4234,6 @@ <h3 id="check-upstream-and-keep-alive-error"><code>Check Upstream and Keep Alive
 <p><strong>Consequence</strong>: any required sync of your <abbr title="a copy of code in a github repository other than the original">fork</abbr> is skipped and build is skipped</p>
 <p><strong>Solution</strong>:</p>
 <ul>
-<li>For <code>Loop</code>: wait for 3.6.0 release (coming soon), all other apps are updated</li>
 <li>Manually sync your <abbr title="a copy of code in a github repository other than the original">fork</abbr> of the <abbr title="contains project files and each file's revision history">repository</abbr>: <a href="../bb-update/#update-fork" target="_blank">Update <code>Fork</code></a></li>
 <li>Manually start your build: <a href="../bb-update/#build-the-app" target="_blank">Build</a></li>
 </ul>
@@ -4248,7 +4247,7 @@ <h3 id="most-common-mistakes">Most Common Mistakes<a class="headerlink" href="#m
 <p class="admonition-title"><abbr title="Apple certificate is used to sign your iOS or Mac apps - tied to but different from your permanent Developer ID">Certificate</abbr> is missing</p>
 <p>If you get this build error message: <code>No code signing identity found and can not create a new one because you enabled</code>, you do not have certificates needed to run the build.</p>
 <ul>
-<li>See <a href="../bb-update/#renew-certificate" target="_blank">Renew Certificates</a></li>
+<li>With <code>Loop 3.6.0</code> and newer, this should not happen. Make sure you <a href="../prepare-fork/#add-variable" target="_blank">Add Variable</a> to automatically renew certificates.</li>
 </ul>
 </div>
 <p>These are some of the most common errors to date.</p>
@@ -4298,13 +4297,12 @@ <h3 id="annotation-without-clear-message-certificates">Annotation without Clear
 <p>This is an example of a message that is not terribly descriptive - which is why it is shown here. In this case, you can click on just the one job that failed. There will be less to sort through to find your error. The most likely reason for this error is <a href="#error-could-not-create">Error: Could not Create</a>.</p>
 <h3 id="missing-certificates">Missing Certificates<a class="headerlink" href="#missing-certificates" title="Anchor link to this Header on this Page">&para;</a></h3>
 <blockquote>
-<p>Coming soon: when <abbr title="Latest release with major updates">Loop 3</abbr>.6.0 (or newer) is available, certificates will be automatically renewed if your developer account is up to date, all agreements are signed and you completed the new <a href="../prepare-fork/#add-variable" target="_blank">Add Variable</a> step.</p>
-<p>After <abbr title="Latest release with major updates">Loop 3</abbr>.6.0 is released, the first attempt to build will update the files required for automatic certificate creation. The second attempt to build will use the new files. So if the first attempt with <abbr title="Latest release with major updates">Loop 3</abbr>.6.0 fails, try again.</p>
+<p>With <code>Loop 3.6.0</code> or newer, certificates are automatically renewed if your developer account is up to date, all agreements are signed and you completed the new <a href="../prepare-fork/#add-variable" target="_blank">Add Variable</a> step.</p>
 </blockquote>
 <p>If your certificates have expired, you will see this error when you try to build. It does not have a clear annotation. The error string starts with: <code>No code signing identity found and can not create a new one because you enabled</code>.</p>
-<ul>
-<li>See <a href="../bb-update/#renew-certificate" target="_blank">Renew Certificates</a></li>
-</ul>
+<blockquote>
+<p>The first automatic build when <abbr title="Latest release with major updates">Loop 3</abbr>.6.0 is released will update the files required for automatic certificate creation. The next automatic build will use the new files. So if the first attempt with <abbr title="Latest release with major updates">Loop 3</abbr>.6.0 fails, try again.</p>
+</blockquote>
 <p align="center"><img alt="graphic showing missing distribution certificate" src="../img/missing-distribution-certificate.png" width="800" /></p>
 <h3 id="annotation-without-clear-message-build">Annotation without Clear Message (<em>Build</em>)<a class="headerlink" href="#annotation-without-clear-message-build" title="Anchor link to this Header on this Page">&para;</a></h3>
 <p>The <abbr title="Graphics Interchange Format (GIF) can be used for small animations and low-resolution video clips">GIF</abbr> below shows a failure of&nbsp;<em><span translate="no"><em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> Action: 4. Build <abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></span></em>&nbsp;. The nice messages have not been added to this yet - you will have to follow the <a href="#find-the-error">Find the Error</a> instructions, but now, you are automatically taken to the correct section so there is less of the log to deal with.</p>
@@ -4580,11 +4578,7 @@ <h3 id="error-could-not-find-an-app-on-app-store-connect"><code>Error: Could not
 <li>
 <p>Make sure you completed the <a href="../prepare-app/#create-loop-app-in-app-store-connect">Create <abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr> App in App Store Connect</a> Step</p>
 <ul>
-<li>Once you've resolved that step, run these <em><abbr title="a custom application for the GitHub Actions platform that performs a complex but frequently repeated task; specifically used to build Loop from a browser">Actions</abbr></em> again:<ul>
-<li><code>Create Certificates</code></li>
-<li><code>Build Loop</code></li>
-</ul>
-</li>
+<li>Once you've resolved that step, run <code>Build Loop</code> action again</li>
 </ul>
 </li>
 <li>
@@ -4620,9 +4614,8 @@ <h3 id="error-provisioning-profile"><code>Error: Provisioning Profile</code><a c
 <li><code>error: Provisioning profile "match AppStore com.***.loopkit.Loop.Loop-Intent-Extension</code></li>
 </ul>
 <p>Return to <a href="../prepare-app/#identifiers-for-the-loop-app">First-Time: <abbr title="names of modules found on your Apple Developer Identifiers page that are required for GitHub build method">Identifiers</abbr> for the <code>Loop</code> app</a> and make sure you followed all the steps.</p>
-<p>You must create certificates again before you can build <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em>:</p>
+<p>You can build <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em>:</p>
 <ul>
-<li>Action: <code>Create Certificates</code></li>
 <li>Action: <code>Build Loop</code></li>
 </ul>
 <h3 id="error-a-new-one-cannot-be-created-because-you-enabled"><code>Error: A new one cannot be created because you enabled</code><a class="headerlink" href="#error-a-new-one-cannot-be-created-because-you-enabled" title="Anchor link to this Header on this Page">&para;</a></h3>
@@ -4817,7 +4810,7 @@ <h3 id="delete-identifiers">Delete <abbr title="names of modules found on your A
 </ul>
 <p align="center"><img alt="steps to delete a given identifier" src="../img/delete-identifiers.svg" width="700" /></p>
 <p>If coming here because you enter the wrong <code>TEAMID</code> in <code>Secrets</code> - return to <a href="#rerun-steps-with-correct-teamid">Rerun Steps with Correct <abbr title="One of 6 Secrets: Apple Developer account member number">TEAMID</abbr></a> when you've deleted as many identifiers as you can.</p>
-<p>After you delete identifiers, you must add them back before you can build a given app. Configure them and create certificates before you can build again.</p>
+<p>After you delete identifiers, you must add them back before you can build a given app. Configure them and build again.</p>