Version Updates

Did you get a Check Upstream and Keep Alive  error for any app where you use Browser Build method? Follow that link for the solution.

Did you get a “No code signing identity found and cannot create a new one because you enabled `readonly`” error? Please see this link: Interim Fastlane Update.

For information about updates to Apple OS and Xcode versions, as well as Loop and Trio, click the links below:

Loop-dev

All Loopers who are not actively involved in development and testing should be using Loop-main. 

iOS / Apple Updates

We recommend that all loopers treat their phone as a medical device.  Please exercise caution when updating your phone’s iOS, especially for a major update such as iOS 18 to 19.  Minor updates are typically less problematic, but we test every update to be sure.  Auto updates should be off.

Turn off auto-update

Do not set your Loop phone to auto-update its iOS version 

In iPhone Settings, go to General / Software Update / Automatic Updates.

  1. Turn on “Automatic Downloads”
  2. Turn off “Automatic Updates”

Once you upgrade the iOS, it can be very difficult (sometimes impossible) to downgrade.

It’s a good idea to do the same on your computer.  Both the operating system and Xcode should have auto-update turned off. But please, update as soon as the all-clear is sounded.  Updates can provide very important security fixes as well as nifty new features.

Mac-Xcode Builders Only

Should I update to iOS18.x or higher?

Yes!  You should update.  iOS 18 is recommended.

Your Mac must be capable of running macOS 14.6 but soon will need macOS 15.

How to build Loop to an iOS 18.x or higher phone

  1. Update your macOS to the latest it can support (macOS 15.4.1 preferred)
  2. Download Xcode 16.2 or newer
  3. Use the Build Select Script to download fresh Loop code and rebuild

If you find that your macOS won’t update, then a Browser Build is for you.

Developer Mode

This has gotten more complicated recently. Please refer to the LoopDocs write-up on Developer Mode.

What are the latest “tested” versions?

The Versions of macOS and Xcode that you need are based on your phone’s iOS.  These Versions have been tested to operate and build Loop-main, Loop-dev, LoopFollow, LoopCaregiver, and Trio.  This table includes the latest tested versions of iOS, along with the compatible minimum Xcode and macOS versions.

Latest Tested Version of
iOS [Release Date] 

Latest Tested Version of Xcode          [Release Date] 

Minimum OS 
[Release Date]

iOS 18.5

[12 May 2025]
This update turns on Automatic iOS updates.  Once your update is complete, please disable Automatic Updates in iOS Settings/ General/ Software Update!

Xcode 16.4 (16F6)

[28 May 2025]

Sequoia 15.2 or later

[11 December 2024]

 

iOS 16.7.7
[21 March 2024]

Xcode 14.3
[1 June 2023]

15.2 is latest tested version

macOS Ventura 13

    Loop Updates

    Loop Recent Release History

    • Loop 3.6 was released on 23-April-2025, see details here.
      • Add Automatic Certificate Generation and Renewal, which requires a new Browser Build Variable
      • Implement updates to minimize Dexcom G7 outages
      • Add various bug fixes
      • For Browser Builders, adds TestFlight updates required by Apple as of 24-April-2025
        • One time only – you must manually update your fork, then the automatic builds can happen again
        • This is because of the Check Upstream and Keep Alive  error
    • Loop 3.4.4 was released on 12-October-2024, see details here.
      • Fix the expiration date for GitHub build actions and for Mac-Xcode builds
      • Loop 3.4.4 was initially released on 9-October, but inadvertently removed the improvements from v3.4.3.  If you built Loop 3.4.4 between 9-October and 12-October, be sure to update to the latest version

      Loop Customization Updates

      • When updating from Loop 3.4.4 to Loop 3.6.0:
        • Browser Build users must remove 2 customizations from their build_loop.yml files: “bolus_display” and “g7_scan”. Both of these customizations are included in Loop 3.6.0. If you leave them in, your build will fail. Be sure that the last customization you have in your build_loop.yml file does not end with a continuation character. If those directions are not clear for you, please ask for help.
        • Users of the Dana pump – Browser Builders – please modify your build_loop.yml file to use the new version of the pump addition found at this link.

      Trio Updates

      If you need help, please ask on Facebook or Discord.

      Trio Release History

      • Trio 0.5.0 was released on 16-May-2025, see details here.
      • Trio 0.2.5 was released on 22-April-2025, see details here.
      • Trio 0.2.3 was released on 28-January-2025, see details here.
        • Automation added to detect invalid or expired certificates and create new ones
          Requires addition of a Variable

      Interim Fastlane Update

      There is an error that has been showing up with increasing frequency until it now happens every time.

      How do I know if I have the problem?

      • Go to your repository, select Actions: Build
        • If it succeeds you do not have a problem and you gave yourself 90 days
        • If it fails and you see this error: “No code signing identity found and cannot create a new one because you enabled `readonly`” then you cannot build until the code is updated

      Background: The Browser Build method uses code called fastlane to connect GitHub and Apple. With recent changes at Apple, fastlane needs to be updated to match.

      The status, as of 10 June 2025, is as follows:

      • If we use the just released version of fastlane, 2.228.0, you can build again
        • But, this version has not yet been fixed to allow the creation or update of Identifiers
          • If you run Add Identifiers, that action will fail
          • The good news is that Create Certificates and Build will work, so you can get an updated app in your TestFlight
        • If you are a new builder – that means you would have to create Identifiers manually – not hard, but tedious
        • If you are a returning builder, no worries, you can use a branch where we incorporate fastlane 2.228.0 and build as before
      • Why is this not available yet?
        • It takes time and testing to bring in updates
        • If you have only a few days until your app expires – then please reach out for help
          • Give us your URL for the app you need to build
          • We will explain how to update your fork to use fastlane 2.228.0
        • Otherwise, wait until everything gets fixed and you will see updates coming into all the apps and the automatic build feature will build the app for you

      What are other options? Building with a Mac still works.

      More Information

      You should always be in a position to build Loop, if necessary. The best practice is to upgrade your build computer (Mac) before upgrading the iOS on your iPhone.  Of course, that’s your choice.

      Bookmark this page!  {DO THIS NOW!} Come back when you have a version question in the future.

      This page will be kept up-to-date as new versions are released.  You can also sign up for the newsletter, but new version updates may not always be included in the newsletter.  This page is your best “one-stop shop” to answer general questions about versions and compatability.