New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"app has stopped" pushing notif when the app already quit #10
Comments
on different device, theres no error popup, but the notification didnt show up at all got this error instead on the logcat : |
What's android version do u use ? |
I have same issue. |
What's Unity version ? |
Right now I'm using Unity version 5.2.3p1 |
Hi! Thx for great plugin! U mast modify AndroidManifest.xml. I think so. Pls fix that |
Try new version, and open new issue if doens't fixed |
Hi Agasper, |
hey, i got a problem when try launching notif when the app is not active
when i launch the app the notif can come out fine, but not when its off
i use unity 5.2.3 , and the got the exact manifest like yours
i only run the SendRepeatingNotification once on start function with 10 seconds delay
heres the logcat:
--------- beginning of /dev/log/system
W/BroadcastQueue( 478): Unable to launch app bundleIDhere/10183 for broadcast Intent { flg=0x14 cmp=bundleIDhere>/net.agasper.unitynotification.UnityNotificationManager (has extras) }: process is bad
V/AlarmManager( 478): triggered: flg=0x14
V/AlarmManager( 478): Pkg: bundleIDhere
W/BroadcastQueue( 478): Unable to launch app bundleIDhere/10183 for broadcast Intent { flg=0x14 cmp=bundleIDhere>/net.agasper.unitynotification.UnityNotificationManager (has extras) }: process is bad
V/AlarmManager( 478): triggered: flg=0x14
V/AlarmManager( 478): Pkg: bundleIDhere
W/BroadcastQueue( 478): Unable to launch app bundleIDhere/10183 for broadcast Intent { flg=0x14 cmp=bundleIDhere>/net.agasper.unitynotification.UnityNotificationManager (has extras) }: process is bad
V/AlarmManager( 478): triggered: flg=0x14
V/AlarmManager( 478): Pkg: bundleIDhere
how do i fix it?
thank you in advance
The text was updated successfully, but these errors were encountered: