Will changing the targetSdk to 35 break this plugin? I tried it and noticed a slight delay in the alarm ringing — about 1 to 2 minutes. #375
-
|
Will changing the targetSdk to 35 break this plugin? I tried it and noticed a slight delay in the alarm ringing — about 1 to 2 minutes. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @anujjainwork, no I don't think targetSdk 35 could break the plugin. However, target 34 introduced a breaking change with You can check the android installation steps, I show how you can grant exact alarm permission: Let me know if it helps reducing the delay. |
Beta Was this translation helpful? Give feedback.
Hi it did not help but I used AlarmManager().setAlarmClock for android 12+ and now it works perfectly without delay.