Loop 3.6

Apr 22, 2025 | Announcements, Build Help | 0 comments

Loop 3.6.0 was released on 23 April 2025

Most of the updates relate to Browser Builds and to improvements in Dexcom G7 connectivity.  You can see the complete list here.  

Mac-Xcode Builders should follow the detailed instructions in LoopDocs; new Browser Builders should follow these detailed instructions in LoopDocs. If you need to update your Browser Build, there are some one-time build steps that are required when you migrate from Loop 3.4.x to 3.6.x:  

  1. ENABLE NUKE CERTS
  2. May need to modify Customizations
  3. Sync fork
  4. Build (and Enable Build Workflow, if required)

Check Upstream and Keep Alive

Coincidentally, with the release of Loop 3.6, we have seen an unusual error, Check Upstream and Keep Alive.  This error is a result of GitHub suspending a repository that Loop, Trio, LoopFollow, LoopCaregiver, and xDrip4iOS (collectively referred to as “All Apps”) rely upon to keep our repositories alive.  All builds will fail with a Check Upstream and Keep Alive error.  When you get this error, you will need to Sync fork and Build to successfully build your apps.  For complete details, see LoopDocs.

LoopWorkspace: Enable Build Workflow

On April 30, 2025, LoopWorkspace Build workflows were disabled in GitHub.  This issue impacts LoopWorkspace only.  It does not impact Trio, LoopFollow, LoopCaregiver, or xDrip4iOS  The instructions below will help you through this new step (it’s really just one additional click).

ENABLE_NUKE_CERTS

In order to utilize the new automatic certificate renewal feature that was added to Loop 3.6.0 and higher, you’ll need to add a new Variable.  Variables are located in GitHub, in the same location as your Secrets.  The exact location will depend upon whether you build using a GitHub organization or a personal account.

If you use a personal account, click on your LoopWorkspace repository.  If you have other repositories, just follow these same steps for each of them.  The automatic certificate renewal is available for LoopFollow, LoopCaregiver and Trio too.

If you build using a GitHub organization and have already added this variable for Trio, LoopFollow or LoopCaregiver, there’s nothing for you to do.  Otherwise, click on your organization name.

  1. Choose settings
  2. Scroll down to select Secret and variables
  3. Choose Actions
  4. Choose Variable
  5. Tap on “Create new organization variable” or “Create new repository variable”
  6. Add the variaable ENABLE_NUKE_CERTS
  7. Add the value true
  8. Add Variable.

When you’ve finished adding your new Variable, your screen should look similar to the images below.

Delete Customizations when Upgrading to Loop 3.6

Applies only to Browser Builders who have customized with bolus_display and g7_scan:

Find your LoopWorkspace repository in GitHub

  • The URL you see should be similar to the one below (for your username)
https://github.com/username/LoopWorkspace/blob/main/.github/workflows/build_loop.yml
  1. Click Code.
  2. Choose github/workflows.
  3. Choose build_loop.yml
  4. Click the pencil icon.
  5. Scroll to your customizations
    • Locate your customizations around line 285
    • Delete these customizations (they’ve been added to Loop 3.6, so the customizations are no longer necessary):
      • g7_scan
      • bolus_display
    • Make sure that your final customization does not end with \
      • Detailed instructions to edit customizations can be found here
  6. Commit Changes.
  7. Commit directly to your branch.

Sync Fork- All Apps

  1. Navigate to
https://github.com/username/repository_name/tree/main

Substitute your GitHub username for username, your repository name for repository_name (for example, LoopWorkspace, LoopFollow, LoopCaregiver or Trio), and your branch for main if you’re not using the main branch.

  1. Sync fork (see image below)
  2. Update Branch
    • Do Not delete your commits – If your pop-up gives you the option to Delete xx Commits.  These are typically customizations that you’ve added, and only the 2 above need to be removed.

Build- All Apps

  1. Go to
https://github.com/username/repository_name/actions

Copy and paste the link above into your browser tab’s URL, but substitute your GitHub username for username and your repository name for repository_name, (for example, LoopWorkspace, LoopFollow, LoopCaregiver or Trio).

 

  1. Build (see Steps 2-5 in image below)
  • If your Build workflow is disabled, you will see the Disabled notation below and will need to enable the workflow.
  • If your Build workflow is not disabled, you will not see step 3.

    Need Help?

    Please don’t struggle.  Don’t delete your repositories, variable, or anything else.  Post on Facebook with your GitHub username or organization and someone will help you troubleshoot.