Manual Notes

This update to LoopFollow, v2.7.0 does not affect the LoopFollow code itself but it does:

• Enable people to use Browser Build again when their Identifiers are already configured
  • Before this update, the actions that automatically renewed certificates were not working, so some people were getting build failures - the update to fastlane 2.228.0 fixes this problem
  • The GitHub action Add Identifier will still fail with this version
  • The failure is because Apple removed a capability in May 2025 and the fastlane code, used to link GitHub actions with Apple Developer credentials, is only partially updated
  • If necessary, the Identifiers can be manually added to the Apple Developer site
• Automatically increment the dev version by one number for each change compared to the released code
  • Whenever new features are merged to the dev branch, the version number is now incremented
  • Released versions are M.N.0
  • As soon as a change is made to the dev branch, it becomes M.N.1 for the first change, M.N.2 for the next change, etc.

Browser Builders: Disable the DO NOT RUN Action

The process by which the dev version number is automatically incremented by the developers uses a GitHub action - similar to what is used for browser build. Once you update to this release, you will see an extra job as shown in the graphic below.

Optional

After you follow the steps in the graphic to disable the workflow, you won't see a skipped job in your fork when you do your next update.

1. Select the [DO NOT RUN] action
2. Click on the three dots at upper right
3. Choose to disable the workflow

What's Changed (Automatic Notes)

• Add auto bump of dev version on push by @marionbarker in #401
• Update to fastlane 2.228.0 by @marionbarker in #406

Full Changelog: v2.6.0...v2.7.0

Manual Notes

This update brings in one bugfix. PR #402

When we previously fixed a bug for Trio that was causing a crash, we inadvertently created a display bug for Loop. With this release, overlapping (Trio) and indefinite (Loop) overrides are now handled correctly for both OS-AID systems.

What was the problem?

• indefinite overrides created by Loop were incorrectly displayed as 5-minute events until they ended
• once terminated, they were updated with the correct duration and rendered properly
• with this update, they are rendered properly the entire time they are active

What's Changed (automatically generated)

• Fix for Loop indefinite overrides by @bjorkert in #402

Full Changelog: v2.5.0...v2.6.0

Manual Notes

This update brings in one bugfix: PR 400: Fix for crashes related to overrides

In plain language:

• The manner in which override segments were displayed sometimes caused LoopFollow to crash
• The method was updated to prevent crashes.

What's Changed (Automatically Generated)

• Fix for crashes related to overrides by @bjorkert in #400

Full Changelog: v2.4.0...v2.5.0

Manual Notes

Enable the Trio Remote Command functionality to be used when building LoopFollow with the main (released) branch.

This capability was available for testing with the closed beta testing for Trio; but to avoid confusion, it was not displayed as an option when using an app built from the main branch of LoopFollow.

Now that Trio 0.5.0 and newer is available at nightscout/Trio; users will want to be able to access those settings from a released version of LoopFollow.

This update makes that possible.

To use Trio Remote Control with Trio. Must build using the dev branch of Trio.

To configure Trio Remote Control, see https://triodocs.org/configuration/settings/features/remote-control/.

What's Changed (Automatically Generated)

• Remove Trio limitation by @bjorkert in #395

Full Changelog: v2.3.1...v2.4.0

Manual Notes

Starting April 21, 2025, a GitHub Build Action error in the Check Upstream and Keep Alive step was observed for the Open-Source apps that use that feature. This included Loop, Trio, LoopFollow, LoopCaregiver, and iAPS.

These apps relied on a third-party repository that kept our forked app repositories alive longer than the 60-day limit that GitHub established. GitHub disabled that repository for violating the GitHub terms of service. The loss of that repository caused all builds, manual or automatic to fail in the Check Upstream and Keep Alive section. This happens before the build action syncs the fork.

In this release, the LoopFollow repository was updated to resolve this error.

You will need to manually Update the Fork and then use Actions to Build your app.

Other changes include

• modifications to what is found in the log
• detection of stale enacted time stamps, which are ignored
• addition of the charging indicator (that works only with Trio closed beta - coming soon to Trio)

What's Changed

• Log app version and build details by @bjorkert in #389
• Skip task scheduler logging by @bjorkert in #392
• Add logging for remote commands by @bjorkert in #390
• Ignore old enacted timestamps by @bjorkert in #391
• Display charging indicator by @bjorkert in #393
• disable keepalive-workflow because the repo is no longer available by @marionbarker in #397

Full Changelog: v2.3.0...v2.3.1

Manual Notes

The first automatic build for LoopFollow and it has automatic certificate renewal included:

• Be sure to add the Variable 'ENABLE_NUKE_CERTS` and set it to true if you haven't already done so
• See LoopDocs: Add Variable

What's Changed

• Omnipod DASH heartbeat by @bjorkert in #378
• Auto update and build LoopFollow on schedule, auto renew certificates by @marionbarker in #383
• Adjust ISF Unit Detection Threshold from 15 to 16 by @bjorkert in #386

Full Changelog: v2.2.12...v2.3.0

Manual Notes

LoopFollow 2.2.12 was released just one day after LoopFollow 2.2.11.

• A recent code change introduced crashes in recent versions.
• We believe we've now identified the source of the issue and have fixed it.

We're sorry for the inconvenience and appreciate your patience. Please update and rebuild the app for the best experience. Thanks for your support!

More Details

The issue was caused by the timer being accessed from both the main thread and the queue handling tasks, leading to race conditions. The fix replaces it with a DispatchSourceTimer, which runs on a dedicated dispatch queue, ensuring the timer is only accessed from the correct thread.

What's Changed

• Task Scheduler Thread Safety Improvements by @bjorkert in #384

Full Changelog: v2.2.11...v2.2.12

Manual Notes

📢 LoopFollow 2.2.11 is here! 🚀

This update brings some exciting new features and improvements to make LoopFollow even more reliable and helpful.

Warning - we only thought we had fixed the intermittent crashes with v2.2.11. We tried again with v2.2.12 and we think we got it. So please skip 2.2.11 and build 2.2.12 to get all the new items mentioned here without the crash issues.

Here’s what’s new:

🔋 Battery Drop Alarm – A new alarm that can alert you if the battery is draining faster than usual. Perfect for catching situations like a forgotten flashlight left on!

🎨 Contact Improvements – You can now choose colors for contacts and have the option to display trend and delta in separate contact cards for better clarity.

⏳ Expected BG Delay

• For Bluetooth heartbeat devices, the expected BG delay value is reported to help you choose the device that provides the shortest delay in BG readings for the looper's CGM
• This is especially useful if you are saving your old G7 Sensors so you have a choice
• Pro-tip: note the Bluetooth device name for the G7 Sensor that is in use and when you remove it, write it on the used G7 sensor

🔧 Stability & Logging Enhancements – (we did fix some crash reasons but missed one)

• ✅ Improved internal task management to reduce crashes.

• ✅ Added logging when an alarm is triggered to help with troubleshooting.

Enjoy the new features!

What's Changed

• Add battery drop alarm by @dnovosel in #370
• Contact improvements by @bjorkert in #374
• Color selection for Contact Image by @mikebash in #349
• Add rileylink offset calculations by @dsnallfot in #376
• Task improvements by @bjorkert in #379
• Estimated bg delay by @bjorkert in #375
• Add alarm log and some cleanup by @bjorkert in #381

New Contributors

• @dnovosel made their first contribution in #370

Full Changelog: v2.2.10...v2.2.11

Manual Notes

• This release restores the display of prediction lines generated by Trio version 0.2.3 and earlier
  • The prediction lines display for Trio 0.2.3 and earlier was modified by mistake in v2.2.9

What's Changed

• Predictions for released version of Trio by @marionbarker in #373

Full Changelog: v2.2.9...v2.2.10

Manual Notes

Highlights of this update.

• Add ability to Set and Cancel Overrides on the Loop phone (when properly configured)
• Add ability to use an external bluetooth device (such as RileyLink or expired Dexcom device) to act as a heartbeat and save phone battery while making alarms more reliable
• Add a logging capability with files that can be examined or shared
• Various bug fixes and code improvements

Please refer to the Loop and Learn documentation page for more information on how to configure and use the LoopFollow app.

What's Changed

• Update Browser Build files to fastlane 2.225.0, macos 15 and Xcode 16.2 by @marionbarker in #346
• Fallback on suggested if enacted is not present by @bjorkert in #345
• Fix crash by safely handling optional casting for ‘duration’ by @bjorkert in #347
• Fix date parsing for Temp Basals using ISO8601DateFormatter by @bjorkert in #350
• Bluetooth Heartbeat by @bjorkert in #351
• Bugfix, show delta string with +- sign in notifications by @bjorkert in #367
• Prevent Rec. Bolus Alarm from Repeating by @bjorkert in #364
• Limit displayed override duration to 'Hours of Prediction' after current time by @bjorkert in #363
• Enable Setting and Canceling Loop Overrides by @bjorkert in #362
• Improved Duplicate Handling in Nightscout BG Data Processing by @bjorkert in #365
• Alert missed reading stepvalue change by @bjorkert in #366
• Adapt LoopFollow to Trio 1.0’s Updated Device Status Upload Behavior by @bjorkert in #368

Thanks also to @dsnallfot for his help.

Full Changelog: v2.2.8...v2.2.9