-
Notifications
You must be signed in to change notification settings - Fork 371
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]: ANRs coming from com.onesignal.common.modeling.Model.initializeFromJson #2236
Comments
@isles1217 Great to hear that bulks of ANRs have been resolved in our latest release! We are currently investigating this particular stack trace and will provide an update once a new release is available. |
@isles1217 The stack trace indicates that the operation is enqueuing and waiting on the main thread. However, the 5.1.26 release has moved this step to the background thread. Could you double-check that this isn't happening in your latest version? Additionally, could you provide another stack trace that includes line numbers for these lines of code?
|
I'm also seeing this with the latest 5.1.26 Here's the stacktrace:
|
What happened?
This is a follow up issue to #2230. A bulk of our ANRs have been fixed following the release of 5.1.26, but I'm still seeing ANRs with one particular stack trace. We really appreciate the work on reducing these ANRs, and I'm hoping this particular trace gets rid of the last major culprit. Thanks for the improvements so far!
Steps to reproduce?
What did you expect to happen?
OneSignal to not block the main thread
OneSignal Android SDK version
5.1.26
Android version
13, 12, 11
Specific Android models
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: