Android: denying the microphone permission exits the app silently
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- android, cpp
- Domain
- audio-video-rtc, mobile-dev
Research direction
Start at src/main.cpp:833-841 and trace the Android permission-denial path that returns immediately after RECORD_AUDIO is denied. Reproduce the behavior on Android and inspect logcat; done means the app reports the missing microphone permission before exiting, with the exit status behavior addressed as described in the issue.
Written by the indexing model from the issue text.
Description
MY LLM WROTE:
As promised in #2570 — on Android, denying the RECORD_AUDIO permission exits the app with no message of any kind: no window, no dialog, no toast. The user taps the icon and stays on their home screen.
It is deliberate (src/main.cpp:833-841, a bare return 0), and the exit status is 0, so nothing marks it as a failure. The trap is that Android sets USER_FIXED on an explicit deny, which suppresses the permission dialog on every later launch — so the app is then permanently unstartable with no in-app way back and no explanation.
Reproduced 8/8 on two builds (mainline 3.12.3dev-1f9667ec and a PR build), Android 16 / arm64 / Qt 5.15.2, one device. exit app 0 appears in logcat ~200 ms after the library loads.
A message naming the microphone permission before exiting would fix it. Non-zero exit status would help tooling too.
@ann0see — you suggested denied permissions cause bad states on all platforms. Likely, but I only tested Android, and this mechanism is Android-specific, so I'd treat the desktop cases as separate.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 248
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 8
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.
More from jamulussoftware/jamulus
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jamulussoftware/jamulus#3953 · 2 comments ·
-
AI bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jamulussoftware/jamulus#3901 · 4 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
jamulussoftware/jamulus#3961 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
jamulussoftware/jamulus#3958 ·
-
refactoring
jamulussoftware/jamulus#3955 · 1 comment · 1 assignee ·
All issues in jamulussoftware/jamulus
Similar issues
-
task
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vsanthanam/JBird#429 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
es-ude/OnDeviceTraining#459 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bilelmoussaoui/gobject-linter#199 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bradcypert/plum#53 ·