-
Notifications
You must be signed in to change notification settings - Fork 368
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
[Bug]: android.view.WindowManager$BadTokenException - Unable to add window #2014
Comments
@albertoderodrigo thank you for reporting; we'll look into this. |
same here, only see it in Google's Play store vitals.
|
any news? this is our number 1 crash. please fix it. |
We faced the same problem, and it's our number 1 crash as well (application with millions of active users). |
Can you confirm whether you have tried updating to the latest release, and if the issues persist? Have you also reviewed #2048? |
@marclucraft, we are using version 5.1.8. The fix for this issue is not mentioned in the changelog for 5.1.9. |
We receive many bug reports like this: Stack trace
Currently running 5.1.3, upgraded to 5.1.6, will let you know if this is not resolved, and hopefully won't forget to tell you that it is |
…indow OneSignal#2014 android.view.WindowLeaked:
running |
@marclucraft, Hi! Could you tell me what your plans are regarding this crash? The last four months this issue is the most significant crashe on my project. |
@Sergeo-sel – Unfortunately, I am only part of the Support team at OneSignal and cannot answer your question. @jennantilla – anything you can add to this? |
any updates? |
What happened?
I see this error on firebase from your SDK
This could help https://stackoverflow.com/questions/7811993/error-binderproxy45d459c0-is-not-valid-is-your-activity-running
Full log:
io.socialgamesonline.slotcom_issue_e128821ca7d4cb21571b73e42c6bd165_crash_session_65E5B6C4004300016D57E2D4CA33E9FD_DNE_0_v2_stacktrace.txt
Steps to reproduce?
What did you expect to happen?
No errors
OneSignal Android SDK version
5.1.6
Android version
13, 12
Specific Android models
No response
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: