-
Notifications
You must be signed in to change notification settings - Fork 34
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
Recent crash report #109
Comments
Line #6 |
Ok I setup an Android 8.0 emulator and now I see this error about Failed to post notification on channel "null" Which then led me to this change for Android 8.0: https://developer.android.com/guide/topics/ui/notifiers/notifications#ManageChannels So it seems this error has to do with Notification channels.. No idea how to set those up, but just an FYI |
I'm experiencing this issue as well. Have you determined the best way to handle this? Could ti.goosh somehow swallow this error? Or do we have to setup Channels? |
@killroyboy It sounds like you will have to setup channels. It looks like Ti.Goosh doesn't support that yet? What I did for now is to downgrade the target SDK back to 25. It is when you go up above that in targetSDK that Android wants those channels. Problem is Google says they will require target SDK above 25 starting in August, so you can target 25 and submit a build now and then just wait until Ti Goosh has an update to support channels Thats my master plan atleast :) |
@mark22 Thanks. I ended up doing the exact same thing. I'll figure out the channels after the current release. |
Having the same problem, will downgrade target sdk to 25 |
This issue doesn't seem to be caused by channels. Apparently, Android 8 reduced the scope of services and it is now forbidden to start a service in the background. You can reproduce the issue by stopping your app and sending a notification. You will get the same error: java.lang.IllegalStateException on startWakefulService. The GcmReceiver is now deprecated and the JobScheduler should be used instead for Android Oreo and above. Downgrading the target SDK to 25 would be a solution, but Google Play will refuse it after the release of Android P (probably August 2018). |
java.lang.NumberFormatException: this crash I got from android vitals and it's happening for all the users. |
Does anyone know a solution to this? |
I highly recommend using this plugin instead: https://github.com/hansemannn/titanium-firebase-cloud-messaging No crashes and seems to work perfectly. |
This thing has recently started dominating my crash logs (23,975 reports so far.... :)
Any ideas?
The text was updated successfully, but these errors were encountered: