-
-
Notifications
You must be signed in to change notification settings - Fork 120
Description
In the Google Play Console we have quite some ANRs logged that point to the NotificationRestoreReceiver
of this plugin but I do not understand what the issue here is.
This seems to exclusively happen on Honor and Huawei phones (=from the era before HarmonyOS and with Play Store/ Play Services installed obviously)
Only information
Broadcast of Intent { act=android.intent.action.LOCKED_BOOT_COMPLETED flg=0x9000010 cmp=xxx.yyy.zzz/com.telerik.localnotifications.NotificationRestoreReceiver (has extras) }
and nothing much more except native obfuscated traces.
I understand that the AndroidManifest uses the RECEIVE_BOOT_COMPLETED
permission
plugins/packages/local-notifications/native-src/android/app/src/main/AndroidManifest.xml
Line 4 in ccac450
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" /> |
and the intent filters on LOCKED_BOOT_COMPLETED
and BOOT_COMPLETED
plugins/packages/local-notifications/native-src/android/app/src/main/AndroidManifest.xml
Lines 25 to 26 in ccac450
<action android:name="android.intent.action.LOCKED_BOOT_COMPLETED" /> | |
<action android:name="android.intent.action.BOOT_COMPLETED" /> |
and finally, in the receiver this line guards for the BOOT_COMPLETED
Line 28 in ccac450
if (context == null || !Intent.ACTION_BOOT_COMPLETED.equalsIgnoreCase(intent.getAction())) { |
looks all good to me. Still we get these ANRs. Any idea why?
Btw, in Eddy's original plugin, there is also an issue related to this, not resolved as well:
EddyVerbruggen/nativescript-local-notifications#186