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
There is a provisioning profile generated by Xcode/Apple Developer, and that lasts for one year. This decide when the app expires. But users typically don't know when this is, amd itbis NOT 1 year from build date, nor is it related to Dev account expiry date.
In Loop 2.2.6 and FreeAPS (LnL release build 202) you can see the provisioning profile expiration date in the Loop Issue report, and there are also alerts to warn as the date approaches.
This is the commit for Loop adding the expiration date to Issue report: LoopKit/Loop@a29859c
Such a feature would make FreeAPS X support easier in the long run.
Here is some info for other users about how to find the expiration date in Xcode:
There is a provisioning profile generated by Xcode/Apple Developer, and that lasts for one year. This decide when the app expires. But users typically don't know when this is, amd itbis NOT 1 year from build date, nor is it related to Dev account expiry date.
In Loop 2.2.6 and FreeAPS (LnL release build 202) you can see the provisioning profile expiration date in the Loop Issue report, and there are also alerts to warn as the date approaches.
This is the commit for Loop adding the expiration date to Issue report:
LoopKit/Loop@a29859c
Such a feature would make FreeAPS X support easier in the long run.
Here is some info for other users about how to find the expiration date in Xcode:
https://www.loopandlearn.org/loop-expiration-date/
The text was updated successfully, but these errors were encountered: