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.

[anujjainwork]

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.

[gdelataillade]

Hi @anujjainwork, no I don't think targetSdk 35 could break the plugin. However, target 34 introduced a breaking change with SCHEDULE_EXACT_ALARM permission.
Source: https://developer.android.com/about/versions/14/changes/schedule-exact-alarms

You can check the android installation steps, I show how you can grant exact alarm permission:
https://github.com/gdelataillade/alarm/blob/main/help/INSTALL-ANDROID.md#step-5

Let me know if it helps reducing the delay.

[anujjainwork]

Hi it did not help but I used AlarmManager().setAlarmClock for android 12+ and now it works perfectly without delay.