-
Notifications
You must be signed in to change notification settings - Fork 369
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
SecurityException: Caller no longer running, last stopped #638
Comments
@fazalBykea The OneSignal SDK does not use OneSignal actually has it's own copy of OneSignal doesn't use evernote/android-job but they have an issue here that has a bunch of details on this crash. https://github.com/evernote/android-job/issues/255 |
Hello, @fazalBykea I am also facing the same issue and most of them are coming in Android Oero
|
@nishkul Are you able to reproduce this crash? |
This is what i am facing these days. Getting almost 6300 crashes a day. It has to be resolved. Please let me know, what i can do to help you to fix this issue. Caused by java.lang.SecurityException: Caller no longer running, last stopped +622ms because: last work dequeued |
@CodeBoyChd Followed up with you on #673 |
|
请问,你问题解决了吗? |
Description:
We have been observing this crash on our fire base console for the users which have android 8 (Oreo) + devices. Stack trace shows that its your internal method which is causing this fatal exception.
Environment And Device Details
Device Info:
OneSignal SDK Version:
Stack trace Information
99% of our crashes are happening on Android O, with a large number of those users on Samsung devices (but this doesn't seem to be a Samsung-only issue, there are also a fair number of HTC, LG, Google, etc. devices)
If you need more information do let me know.
The text was updated successfully, but these errors were encountered: