nightscout / nightscout/AndroidAPS
Pump/Rileylink connection error messages persist after the failed connection has been resolved
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
If Pump or Rileylink connectivity is lost and subsequently regained, errors/notifications persist regarding the self-resolved problem. e.g.
- Red notification bar that appears in some cases at the top of the dialog with a [snooze] button
- Failed basal adjustment dialogs with the [Mute] button
The situation re. 2) is even worse since if the user ignores the warnings e.g. for 20 minutes, then upon entering AAPS they must click the 'OK' button 4x in order to make the dialog disappear (I presume that it appears every 5 minutes and that after 20minutes of failed basal updates, there are 4 dialogs superimposed upon one another).
Tested on AAPS 3.0 B5
Related to #884
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue concerns Pump/Rileylink connection recovery and the red notification and failed basal adjustment dialogs. Reproduce a recovered connection in AAPS 3.0 B5, then trace the connection-error notification and dialog entry points; done means those warnings are cleared or no longer stack after connectivity returns, including repeated basal-update failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100