You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Click on each **`IDENTIFIER`** in turn and the `Edit Your App ID Configuration` screen will open.
153
152
154
-
1. In the `App Services` column, scroll down to the `App Groups` row
155
-
* Ensure the check box (under the `Capabilities` column) for `App Groups` is checked
156
-
* If the word `Edit` shows up under `NOTES`, return using the `< All Identifiers` button at the top left
157
-
* If the word `Configure` shows up, tap on it
158
-
* This opens the `App Group Assignment` screen
159
-
* Check the box by `Loop`*App Group* that uses your `TEAMID` in `group.com.TEAMID.loopkit.LoopGroup` and then `Continue`
153
+
The example graphic below has numbered steps that match these directions:
160
154
161
-
If you modified settings for an **`IDENTIFIER`**, the `Save` button at the top right will become active. Click on `Save` before leaving this page - otherwise, the change does not take effect.
155
+
1. Looking at the `App Services` column, scroll down to the `App Groups` row and ensure the check box (under the `Capabilities column`) for `App Groups` is checked
156
+
2. If the word `Configure` shows up, tap on it
157
+
* This opens the `App Group Assignment` screen
158
+
* If it said `Edit` instead of `Configure` - you can click to confirm you have the correct App Group but won't need to continue or save if it is correct
159
+
3. Check the box by `Loop App Group` that uses your `TEAMID` in `group.com.TEAMID.loopkit.LoopGroup`
160
+
* Note that if you previously built with Xcode, the name may be different, i.e., `XC group com TEAMID loopkit LoopGroup`
161
+
4. Tap `Continue`
162
+
5. Tap `Save`
162
163
163
-
* Tap on `Save`
164
-
* This opens the `Modify App Capabilities` confirmation screen
165
-
* Click on `Confirm`
164
+
{width="700"}
165
+
{align="center"}
166
166
167
167
If you did not need to make changes, the `Save` button will not be active.
168
168
169
169
* Tap on the `< All Identifiers` button at the top left
170
170
171
171
The full list of Identifiers should be displayed again.
172
172
173
-
Repeat until the 4 Identifiers for the version you are building have the `Loop App Group` configured.
173
+
Repeat until the 4 Identifiers have the `Loop App Group` configured.
174
174
175
175
* If you miss an identifier, the `Create Certificates` step will succeed but `Build Loop` will fail.
Copy file name to clipboardExpand all lines: docs/operation/features/notifications.md
+23-18Lines changed: 23 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -18,35 +18,38 @@ When you tap on the Learn More button, another screen appears. The only option a
18
18
19
19
## Loop App Expiration Notification
20
20
21
-
Profile expiration notification was added with Loop 2.2.5.
21
+
### Expiration on Settings Screen
22
22
23
-
With Loop 3.4 and later, apps installed using GitHub Browser Build method report and alert the user for the TestFlight expiration date. Instead of Profile Expires Soon, the modal alert with say "TestFlight Expires Soon". There is no change to the alert system for apps built with Mac-Xcode method.
23
+
At any time, you can tap on Settings and scroll to the bottom of the screen to see when your app will expire.
24
24
25
-
{width="350"}
26
-
{align="center"}
27
-
28
-
* When fewer than 20 days remain until profile or testflight expiration, you'll get a notification when you open the app but no more frequently than every 2 days
29
-
* When fewer than 24 hours remain, you'll get a notification when you open the app, once every hour at most
30
-
* Simply tap on the `More Info` button of the notification for more information
The graphic below shows the Settings display for a *TestFlight* build (version 3.3 or newer):
33
26
34
-
### Free (7-day) Loop App Expiration Notification
27
+
{width="300"}
28
+
{align="center"}
35
29
36
-
The expiration notification pattern is the same as for the Paid Loop App. You may want to add an [Expiration Notification Customization](../../version/code-custom-edits.md#expiration-notification-customization) to modify the first appearance and frequency of the notification.
30
+
### Expiration Alert
37
31
32
+
Notification before an app expires is reported using this protocol:
38
33
39
-
## Loop App Expiration Date
34
+
* When fewer than 20 days remain, you'll get an alert when you open the app but no more frequently than every 2 days
35
+
* When fewer than 24 hours remain, you'll get an alert when you open the app, once every hour at most
36
+
* Simply tap on the `More Info` button of the alert for more information
37
+
* Build with *Mac*: [Update/Rebuild with *Mac*](../../build/updating.md){: target="_blank" }
38
+
* Build with Browser: [Update/Rebuild with Browser](../../browser/bb-update.md){: target="_blank" }
40
39
41
-
#### For Loop 3.4 and newer versions
40
+
The graphic below show an example expiration alert for a *Mac* build:
42
41
43
-
The testflight expiration data is provided, instead of the profile expiration data, when the app was built using GitHub Browser Build method. When the app was built with Mac-Xcode, the date shown continues to be the profile experation date.
42
+
{width="350"}
43
+
{align="center"}
44
44
45
-
See the [TestFlight or App Profile](../../loop-3/settings.md#testflight-or-app-profile) section at the bottom of the Loop Settings screen.
45
+
> Notification when app expires is available in these versions or newer:
46
+
>
47
+
> * Build with *Mac*: version 2.2.5 or newer
48
+
> * Build with Browser: version 3.3 or newer
46
49
47
-
#### For Loop 3.2.x and newer versions
50
+
###Free (7-day) Loop App Expiration Alert
48
51
49
-
The provisioning profile expiration date is found in the that settings section at the bottom of the Loop Settings screen. This is useful for Mac-Xcode built apps, but may be misleading for GitHub Broswer build method.
52
+
The expiration notification pattern is the same as for the Paid Loop App. You may want to add an [Expiration Notification Customization](../../version/code-custom-edits.md#expiration-notification-customization) to modify the first appearance and frequency of the notification.
50
53
51
54
## Omnipod Beeps
52
55
@@ -114,6 +117,8 @@ This mostly happens when the connection is lost for a longer period of time betw
114
117
115
118
If Loop detects that a bolus was not able to be delivered, it will provide a notification. Bolus failures are usually due to stale pump data. Try fetching recent history from the RileyLink menu to update pump data. Loop will also notify of partial bolus deliveries.
116
119
120
+
**Remember: Carbs are saved when you tap `Save and Bolus` following a meal entry - even if the bolus fails.**
0 commit comments