Trio specific App Group

Is your feature request related to a problem? Please describe.

Currently, Trio uses the same shared app group as Loop, iAPS, and xDrip4iOS. This creates a shared storage container with two other OS-AID applications. This comes with drawbacks:

Potential "zombie" data from other apps due to shared app group read/write permissions.
Risk of data corruption or conflicts when multiple apps share the same app group.

Describe the solution you'd like

Change the build scheme and project setup so that Trio has its own, Trio-specific app group and creates its own isolated shared container. Why?

To prevent unintentional data sharing and ensure data integrity, it's crucial to isolate app data by using unique app groups.
This approach was previously adopted in updating LoopCaregiver to have its own app group, preventing data conflicts with Loop.
Support for this strategy is seen in plans for xDrip4iOS, emphasizing intentional incorporation of shared access rather than unintentional data sharing.

Additional context

Benefits we see are, among others:

Enhanced data integrity and security.
Clear separation of app data, reducing the risk of conflicts.

This establishes a standard for app development within the DIY T1D ecosystem, promoting better integration and reliability.

Technical Details

Adopt a Trio-specific APP_GROUP_ID identifier in the build settings of the scheme. Remove APP_GROUP_ID from xcconfig.

nightscout / Trio