Can't enable "Alarms & Reminders" on Android 14. Version "4.2.5"

[LuongTruong]

Your Environment

• Plugin version: 4.2.5
• Platform: Android
• OS version: Android 14
• Device manufacturer / model: Pixel 6 emulator
• React Native version (react-native -v): 0.72.14
• Plugin config: I follow the instruction of the repository

Expected Behavior

When I update the version to 4.2.5, I expect I am able to enable the "Alarms & Reminders" from app's setting.
With the previous version: 4.1.10, I am able to enable the "Alarms & Reminders" from app's setting.

Actual Behavior

I can't enable the "Alarms & Reminders" from app's setting.

Steps to Reproduce

1. Follow the instruction from the repository and eble to make the app work on both Android and iOS with version 4.1.10
2. Add permission: <uses-permission android:name="android.permission.SCHEDULE_EXACT_ALARM"/>
3. Create intent: ACTION_REQUEST_SCHEDULE_EXACT_ALARM and move users to app's setting screen to enable the "Alarms & Reminders"
4. Change the version from package.json from 4.1.10 to 4.2.5. Then rebuild the app. Users will also move to the app's setting screen, but now they cannot enable the "Alarms & Reminders".

Image 4.2.5 (Not working)

Image 4.1.10 (Working)

Enable

Disable

Context

I tried to:

• Add permission: <uses-permission android:name="android.permission.USE_EXACT_ALARM" android:minSdkVersion="34" /> but nothing happen. Moreover, my app is rejected by Google Play because it is not a clock app or related to clock app.

Debug logs

Everything is built and worked normally, so there is no log.

Please let me know if you have any idea. Many thanks, guys!

[christocracy]

my app is rejected by Google Play because it is not a clock app or related to clock app.

So don’t add the permission USE_EXACT_ALARM. It’s not required.

[LuongTruong]

Hello @christocracy , thanks for the comment. I tried to remove the USE_EXACT_ALARM but still not be able to enable the "Alarms & Reminders" after upgrading the version to 4.2.5

Do you have any other ideas?

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.