Google Play reports our apps as having a defective SDK

troylyndon · March 17, 2024, 6:57am

my Google Play Pre-launch report overview shows a STABILITY issue: Defective libraries, details: Your use of exact alarms is causing your app to crash for some Android users

No where is my app do I have the word ‘alarm’

bgmadclown · March 17, 2024, 10:47am

That warning seems to be an error now.

@vlads I think you should look at that PR to see if it works. That seems to be a priority now.

github.com/coronalabs/corona

Added check to exact scheduling for notifications

coronalabs:master ← zdmitrynsk:update_android_notification_service

opened 11:51PM - 06 Dec 23 UTC

zdmitrynsk

+8 -1

SCHEDULE_EXACT_ALARM, the permission introduced in Android 12 for apps to schedu…le exact alarms, is no longer being pre-granted to most newly installed apps targeting Android 13 and higher (will be set to denied by default). And because the SCHEDULE_EXACT_ALARM permission is now denied by default and the permission grant process requires extra steps from users (the user must minimize the application and change the setting), developers are strongly encouraged to evaluate their use cases and determine if exact alarms still make sense for their use cases. Now for Android devices with SDK greater than or equal to 33, a check has been added for the ability to schedule notifications via AlarmManager.setExactAndAllowWhileIdle(). If this is not possible, then the notification is sent via AlarmManager.set(). For AlarmManager.set() only needs android.permission.POST_NOTIFICATIONS. It can be easily obtained through a modal window using native.showPopup( "requestAppPermission", options ) More information: https://developer.android.com/about/versions/14/changes/schedule-exact-alarms

vlads · March 17, 2024, 3:41pm

Thanks. I merged the PR. Thing I will update documentation and make a new build soon.
Idea is that you have to add the permission to the manifest and check for it