When i restart my phone i get "unfortunately myapp has stopped working"

[Mac956]

Hi, like the title says: When i restart my phone i get "unfortunately myapp has stopped working", if i uninstall your plugin i don't get that error. Thanks in advance again.
Btw is there a way i can make a donation, i'm asking for a lot of changes. Thanks again

[Beefsteve]

I don't have that problem ....but good Idea Mac956. I want to buy something too / or donate anything that could support you Sebastian.

[katzer]

Btw is there a way i can make a donation, i'm asking for a lot of changes.
I want to buy something too / or donate anything that could support you

Thanks, thanks, you are welcome. Your issues and pull request are support enough!

@Mac956 In which cases you are receiving that messages? Have you added notifications with a future date?

[Mac956]

I've tried different ways, but even if i exit myapp and cleared all notifications then i restart my phone, when it's loading all the apps i receive the message "Unfortunatelly, Myapp has stopped". after 2 or 3 sec the message go away, it's like its trying to start Myapp on boot up but fails, i've tried it on a diffrent android phone and it gives the same message, the only modifications i made to the manifest are these:

on activity: android:launchMode="singleInstance" android:persistent="true"

and i'm using these other 2 plugins: org.apache.cordova.dialogs org.apache.cordova.vibration

if i remove the plugin, i open Myapp, then close it and restart, i don't get the error at startup.
Myapp gives notifications based on a timer, and that's it.

Hope this helps. And Thanks in advance again.

[katzer]

OK, I receive that error too.

[katzer]

Should be fixed now (f873a09)

[Mac956]

I tested it and now it's working fine. Thanks

[alan0xd7]

I just encountered this problem with the latest version of the plugin. When the phone is restarted there's a message saying the app has stopped. Currently tested on Android 4.4.4 and 5.0.0 (Genymotion).

My app only needs the notifications displayed right away, so as a workaround I've removed the boot intent filters and permission from AndroidManifest.xml.

Please let me know if you need any details to help fix this, thanks.