Skip to content

Releases: LoopKit/LoopWorkspace

v3.6.2

25 Jun 20:41
fbf2ddc
Compare
Choose a tag to compare

Manual Notes

This release only affect ability to build using the Browser Build method. There are no changes to the Loop app functions.

There were changes at Apple in May 2025 that broke some of the code (fastlane) we use with GitHub Actions to enable Loop to build from a browser.

  • People who already had valid certificates with properly configured Identifiers could build without issue. Those who needed to renew certificates were blocked from building. (fixed with v3.6.1)

  • People who wanted to configure to build for the first time could not run Add Identifiers. (fixed with this release, v3.6.2)

Working Solution

With this release, the GitHub build actions are restored with one caveat for new builders (those who do not already have their Identifiers configured):

  • Apple no longer allows the Time Sensitive Notifications to be configured automatically
  • Time Sensitive Notifications must be enabled for the Loop Identifier manually or the build will fail

LoopDocs is updated with instructions for new builders to manually add Time Sensitive Notifications.

What's Changed (automatically generated)

  • main branch: Use a special version of fastlane to enable Add Identifiers by @marionbarker in #286

Full Changelog: v3.6.1...v3.6.2

v3.6.1

25 Jun 18:31
016c1fd
Compare
Choose a tag to compare

Manual Notes

There were changes at Apple in May 2025 that broke some of the code (fastlane) we use with GitHub Actions to enable Loop to build from a browser.

  • People who already had valid certificates with properly configured Identifiers could build without issue. Those who needed to renew certificates were blocked from building.

  • People who wanted to configure to build for the first time could not run Add Identifiers.

Partial Solution

This release fixes these situations

  • people who already use GitHub Actions (aka Browser Build) and need to have their certificates updated can continue to build
  • people who switch to a different GitHub username (or organization) but use the same Apple Developer ID can build from the new username

The portion of the GitHub action used for new builders that enable them to Add Identifiers with the required capabilities select is still not working with this release. A solution will be provided in the next release.

What's Changed (automatically generated)

Full Changelog: v3.6.0...v3.6.1

v3.6.0

23 Apr 16:32
5bac6d2
Compare
Choose a tag to compare

Manual Notes for Loop 3.6.0 release

Highlights

  • Add Automatic Certificate Generation and Renewal
  • Implement updates to minimize Dexcom G7 outages that were reported over the last few months, possibly related to iOS 18 changes
  • Modify the bolus after meals button to say Save Carbs & Deliver
  • Updates to Omnipod Eros and DASH repositories: some bug fixes, some improved responses
  • Fix a few bugs
    • Fixed: Stale value of the total bolus in the Bolus Progress Display in HUD - UI Bug only
    • Fixed: Glucose change graph 'predicted' effects were inconsistent at different times or between orientations
    • Fixed: Dexcom G7 calibration flags were not decoded correctly
    • Fixed: Dexcom G7 rare but significant date offset for glucose data
      • If the backfillFinished message was not detected and a stale backFill message was applied to a new sensor, the date for that glucose reading would be in error
    • Fixed: The Algorithm Experiments screen could show stale selections - UI Bug only
    • Not Fixed: The Basal Rate section of the Therapy Settings screen does not update until you exit the screen and then return (this will be addressed in a future update) - UI Bug only, and only seen on some phone hardware (like SE phones) with iOS 18

LoopDocs Link

What's Changed (Automatically generated)

Full Changelog: v3.4.4...v3.6.0