Open mastermichi opened 1 year ago
USE_EXACT_ALARM seems to b an alternative. Which is meant for apps which use this permission as a core function. Ours is an alarm clock. So it's core function is to be exact ;) https://developer.android.com/reference/android/Manifest.permission#USE_EXACT_ALARM
Android 13 will deny the SCHEDULE_EXACT_ALARM permission by default for apps targeting API level 33. The protection level of this permission has been changed from “normal|appop” to just “appop” in Android 13, hence it is no longer automatically granted at install time for all apps that request it. However, Android 13 will automatically grant the permission to all apps targeting API level 31-32 in order to maintain backward compatibility. This means that apps targeting API level 33 running on Android 13 will need to explicitly ask the user for permission before they can schedule exact alarms.
-> https://blog.esper.io/android-13-exact-alarm-api-restrictions/