Skip to content
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

Loop Widget does not work #2170

Closed
MrKakk opened this issue May 19, 2024 · 2 comments
Closed

Loop Widget does not work #2170

MrKakk opened this issue May 19, 2024 · 2 comments

Comments

@MrKakk
Copy link

MrKakk commented May 19, 2024

Hello Everyone,

My name is Alex and I’m using Loop since 4 years. Since then, my diabetes and my health improved a lot. So I want to start this message thanking all the people who are making this close loop system possible, you guys are literally saving and improving lives.

The issue I have is that I can’t use a widget on the main menu in my phone. At the moment, a screen appears on the widget and says “Please adopt Containerbackground API”. Therefore I want to ask you, what do I need to do to adopt this API. I will post a screenshot, then you can see what is going on.

To Reproduce
Steps to reproduce the behavior:

  1. Go to main menu iPhone
  2. Click on 'new widget’
  3. Scroll down to 'Loop'
  4. See error

Screenshots
If applicable, add screenshots to help explain your problem.
IMG_3111
IMG_3110

Phone

  • Hardware: iPhone SE 2020
  • OS Version: iOS 17.3 (21D50)

Loop Version

  • Version Number: 3.2.3 (57)
  • Repo: LoopKit/Loop

CGM

  • Device: Dexcom G7
  • Manager app: Dexcom App

Pump

  • Manufacturer: Omnipod (Insulet)
  • Model: DASH

Thanks a lot in advance for your help and support.

Have a nice day, Alex

@marionbarker
Copy link
Contributor

This is fixed in dev branch. Either build dev or wait for @ps2 to release the next version.

Please close this issue because it is a duplicate. See #2124 (comment)

@MrKakk MrKakk closed this as completed May 19, 2024
@MrKakk
Copy link
Author

MrKakk commented May 19, 2024

This is fixed in dev branch. Either build dev or wait for @ps2 to release the next version.

Please close this issue because it is a duplicate. See #2124 (comment)

Thank you very much @marionbarker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants