Pre-launch report: Your use of exact alarms is causing your app to crash for some Android users
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android
- Domain
- mobile
Research direction
Start with packages/capacitor-plugin/android/src/main/java/io/ionic/backgroundrunner/plugin/api/Notifications.kt around lines 192–194 and compare its exact-alarm permission check with the Android 14 documentation. Review the SCHEDULE_EXACT_ALARM declaration in AndroidManifest.xml and reproduce the pre-launch crash if possible. Done means exact alarms no longer crash when the permission is unavailable.
Written by the indexing model from the issue text.
Description
I submitted my app to the Play Store, and it was rejected due to crashing. The cause:
Your app schedules exact alarms without checking whether the SCHEDULE_EXACT_ALARM permission has been granted. This is causing your app to crash for users on Android 14 because the permission is no longer granted by default.
In most cases, alternative methods of scheduling work or inexact alarms are more appropriate. If your use of exact alarms is justified, update your app so that it checks this permission is granted before scheduling.
I checked the official docs. They say check canScheduleExactAlarms() first. However the code seems to indeed do so.
I have added <uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM" />
to AndroidManifest.xml, as specified in the docs.
- Dominant language
- C
- Stars
- 56
- Forks
- 36
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 ionic-team/capacitor-background-runner
-
[Bug]: android notification channel id not used in CapacitorNotifications.schedulePossibly taken @coffeemakr claimed this 18 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
ionic-team/capacitor-background-runner#158 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
ionic-team/capacitor-background-runner#155 · 1 reaction ·
-
Capacitor keeps running old background runnersMay be free again @theproducer claimed this 262 days ago, and no pull request is open. Openbug
ionic-team/capacitor-background-runner#152 · 1 comment · 2 reactions · 1 assignee ·
All issues in ionic-team/capacitor-background-runner
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kubernetes-sigs/security-profiles-operator#3597 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
AFLplusplus/AFLplusplus#2903 ·
-
Clean up stale and inaccurate comments in the platform screen and input filesPossibly taken @RichStephens claimed this today. Open
Difficulty 2/5 Half a day Newbie friendliness 88/100
FujiNetWIFI/fujinet-config#289 ·
Maintainers usually reply within 1 day
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
nasa/cFS-GroundSystem#272 ·