So here’s a report on using the Github Actions+Fastlane+Testflight to implement Loop-dev without needing a Mac, Xcode, or significant programming knowledge! I actually did the “build” step three days ago, but waited to install on my phone via TestFLight today (just in case, with Christmas, visits to relatives, etc.; not worth it not working and having to take the time to rebuild w/Xcode!).
I already have an Apple developer account and a Github account, so I used those. You can use a free Apple Developer account, but you’d have to “build” the app every 7-days; a Github account is free. I carefully followed the directions contained in the second link in the above post (Note: I’d already built Loop-dev with Xcode, so I skipped the sections first timers need to take.) On starting the “build” instruction, I ran into a problem at about the 90 second mark…the build process just stopped…I tried it three more times with the same result (yes, I know the definition of insanity, but Marion Barker [Loop Documentation guru] said it worked for her when an error occurred). Unfortunately, I’m not well versed in the finer points of Swift, Github, and TestFlight, and there wasn’t a good indicator what the problem might be. I retraced my steps through the instructions and decided to check the “signing” of the various swift modules requiring my Apple Developer ID to be inserted, I found one file didn’t have it, so inserted it. I also found the files I had listed didn’t completely match up with what a few others listed on the Loop Zulip Chat discussion groups. I thought not having all the files listed might be a problem, but tried the “build” again with the one file corrected with my Developer ID. The “build” started and the only clue things were progressing correctly was the timer counting the minutes of the build process. The instructions say “Go get a cup of coffee, it will take 20-30 minutes.” They were spot on, the timer stopped at 20 minutes, 21 seconds, and the bright green checkmark indicating a successful build showed up. Shortly after the green check mark showed up, I received an email stating my build had completed. The guidance says another email should arrive from TestFlight with an invitation to access the app. It took a few minutes for that to arrive…to the point I was thinking perhaps all was not well…but then it arrived. Clicking on the link (using iPhone email) opened the TestFlight app which indicated Loop was ready for install. This morning, I clicked on the link again, TestFlight opened, and I selected install. I got a warning a Loop version was already in place and asking if I wanted to replace it; I answered yes, and off it went. My existing Loop app was closed, replaced, and the program re-started. All my data (treatment settings, etc.) was intact (a couple people reported a notification data might be lost, though no one’s reported actually loosing any!). The app seemed to be working well. TestFlight had a selection toggle to install the updated Apple Watch app, it was already selected to do so and when I checked the watch app it seemed completely functional: able to bolus, chart showed BGs, etc. Gave several hours to see if any problems arose, but it’s been solid ever since.
This version of Loop-dev has the capability to run with a Dexcom G7 (been being tested by Looper’s in Germany), so I’ll look forward to implementing Loop with G7 when it becomes available here in the US. Future builds using Github Actions+FastLane+TestFlight are much simpler than Xcode, just follow the “build” step in the instructions; it does need to be done at least every 90 days (four times per year). There have already been a couple of people that have modified the TestFlight build instructions so it automatically builds the latest version and installs to the phone/watch every 7-days so they’re assured of having the latest/greatest version of the code. The great thing about this method, I can build from my phone, tablet, virtually any browser, so if I’m off on a cruise, loose/damage my phone, I can rebuild with a new phone, even my wife’s, just about anywhere!
Note: Loop-dev is “lightly” tested using various pumps (Omnipod Eros, Omnipod Dash, etc.), RileyLinks, OrangeLinks, Raspberry Pi’s, etc. for validation. It is NOT finalized, FDA sanctioned code or software. Use at your own risk and monitor Loop Zulip Chat groups for noted problems, issues, fixes, etc.
If anyone has any questions, feel free to ask. If I don’t know the answer, I’m sure someone else here of FUD can or I can direct you to the right people on LoopZulipChat. To use Loop-dev, you do NOT need to be a programmer, you DO need to be willing to step outside your comfort-zone, read and follow instructions, try something new, and monitor the LoopZulipChat discussion groups. Hopefully Loop 3.0 will result in more “finished” software, albeit not FDA approved, for linking insulin pumps, CGMs, and iPhones. Various similar products (same base code) are available for Android.
