Exposure notification warning when disabling bluetooth, but EN is disabled
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Describe the bug
I moved to a different country without widespread use of exposure notifications, and disabled the notifications in the German Corona Warn App that I had used before. However, I still get warnings from microG when disabling bluetooth, complaining that it cannot do exposure tracking without bluetooth.
To Reproduce
Steps to reproduce the behavior:
- Enable and use exposure notifications with the Corona Warn App.
- Disable exposure notifications in the Corona Warn App.
- Disable bluetooth.
Expected behavior
Nothing should happen, this is just fine.
Actual behavior
I get a warning saying that disabling bluetooth means there cannot be tracking of exposure notifications. This is despite the fact that exposure notifications are disabled! The warning can be discarded, but it pops up again every now and then by itself, and each time I disable bluetooth.
System
Android Version: 11
Custom ROM: LineageOS 18.1
Additional context
I do not want to uninstall the CWA since it contains my scanned vaccination certificates which I'd rather keep (I will need them when visiting Germany).
Contributor guide
No contributing guide indexed for this repository
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
Use the listed reproduction steps on Android 11 with LineageOS 18.1, the Corona Warn App, and microG; begin by tracing the exposure-notification Bluetooth warning behavior. Done means disabling Bluetooth produces no warning after exposure notifications have been disabled, while the normal warning remains applicable when they are enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100