nightscout / nightscout/AndroidAPS
Crash across multiple versions related to medtronic driver (seems resettable)
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
Pump: Medtronic 722
AAPS Versions: 3.2.0.2/3.2.0.4/3.3-dev-B
Description
At 0700 today my app began crashing repeatedly. It would occur at the end of the data download from the pump and would happen every time the initial connect/download would complete. Upgrades of app from 3.2.0.2 -> 3.2.0.4 -> dev did not change behavior.
Moving to virtual pump for a while then moving back to Medtronic driver interrupted the behaviors and seemingly normal function resumed.
Various logs from the impacted periods included.
Reporting bugs
AndroidAPS_LOG_1715360030719.log.zip
AndroidAPS_LOG_1715357887860.log.zip
AndroidAPS_LOG_1715347051272.log.zip
- Note the precise time the problem occurred and describe the circumstances and steps that caused
the problem - Note the Build version (found in the About dialog in the app, when pressing the three dots in the
upper-right corner). - Obtain the app's log files, which can be found on the phone in
/storage/emulated/0/Android/data/info.nightscout.androidaps/
See https://wiki.aaps.app/en/latest/Usage/Accessing-logfiles.html - Open an issue at https://github.com/nightscout/AndroidAPS/issues/new
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
Start by reviewing the three attached AndroidAPS log archives around the crash at the end of the Medtronic 722 data download, comparing the affected app versions listed in the report. Reproduce the initial connect/download sequence if possible and confirm that switching away from and back to the Medtronic driver no longer causes repeated crashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100