-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update app name to Trio #157
Conversation
It is probably easiest to test using a fresh download to a new folder. Otherwise you may have "debris" left-over from other branches. If you choose to use the same folder, clean the build folder and close Xcode workspace. Make sure you only have Trio.xcworkspace folder available (no other *.xcworkspace folder should exist.) Then open Xcode again. It is possible you may also need to clean derived data ('rm -rf ~/Library/Developer/Xcode/DerivedData'). |
The Browser Build test was successful.
|
I started to build in Xcode but stopped it a few seconds after hitting build/run, realizing I should test in Fastlane first. I checked Apple Developer and the org.nightscout.TEAMID.Trio identifier was created by Xcode but not the other three. I did not delete the alive branch, but I built via Fastlane which was successful. I did notice icon names are off, so I'll put together a PR for that shortly. |
I noticed there are still a lot of |
Perhaps @avouspierre could take a look at this? He is about to refactor something, possibly connected to some of this. |
The ones in main.swift are used for a parser that only @itsmojo uses. I suggest you leave those alone for now. I don’t know about the others. |
The use of iaps & iAPS in OmniBLE/OmniBLEParser/main.swift applies to iAPS & Trio as well as any other FreeAPS based app with a Loop style pumpManager. Here's my suggested changes to this file to handle the general case correctly and which will avoid using a specific app name like iAPS or Trio.
|
@itsmojo , will you make the change in OmniBLE, so we can update our submodule? https://github.com/search?q=repo%3ALoopKit%2FOmniBLE%20iAPS&type=code |
I don't think OmniBLE is a blocker at all, so if it doesn't get updated before everything else in this PR is approved we can just update the submodule link whenever that happens. I just amended the Localization commit to include FAX converts. I have one more commit ready to go for After that, I think I can add my ✅ |
The OmniBLEParser/main.swift change to remove iAPS is not a blocker. I will attempt to create a PR for this as I suggested, but it might take me awhile to do this and I don't even know if I have the needed permissions. |
I have permissions to create a branch in Loopkit OmniBLE with changes and can make the PR. Then Trio just needs to update using either the SHA from PR branch or from dev depending on how long it takes to get the PR reviewed. I will DM with @itsmojo to make this happen. |
@avouspierre Looks like you added this line. Is it okay to update that to Same question about this line you added. |
The first line (BGTaskSchedulerPermittedIdentifiers) could be removed because we didn't use a background task with remote notification. I tested (in my current branch) without and seems OK. CFBundleURLName is useful for garmin app when you link garmin connect to the app. You could change it with dynamic variable. You could use BUNDLE_IDENTIFIER as a URL. |
in Shortcuts, HealthKit, FileStorageTests, and URLs
Thanks avouspierre! With that piece in place, I think we're good to merge this into dev now. |
I guess I can't add myself as a reviewer since I began this PR; if I could, I would approve this PR. I tested the latest version using Xcode onto a test phone with Trio on it. |
Re-write of the Contribute section.
Update README.md
After testing, I reviewed the modification to README.md by Magnus and accepted the PR. |
I'll build now :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Built and tested on clean Mac
The following steps were used to update the app name to Trio.
Each step used one or two atomic commits to make it easy to follow for reviewers.
Testing: