-
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
executing service com.onesignal.SyncJobService ANR #1487
Comments
We are also having this issue - many ANRs through console, and many complaints from users. Although we released the latest version of the app in July, this issue just cropped up in the last two weeks when we used OneSignal to announce a new version. I can't replicate it, but our customer support person has been able to. It is somehow related to AssetPack management (our app has about 2 GB of associated data). I believe that the AssetPack threads are locking up as a result of the notification, and returning incorrect information to the app - the end result is our app can't get any information about the installed AssetPacks and believes new AssetPacks should be downloaded (this is false). Since it is waiting for new AssetPacks to download, the app hangs. Environment
Device Information
Stack Information
|
@connyduck @RosHartigan Thanks for the full stack traces. They both contain |
We have |
We have Since I suspect the asset-pack notifications/service is causing a conflict: |
Just noticed this issue being reported in our bug reporting console. Were you able to identify what is causing this and mostly how to avoid this? I'm also using the latest Unfortunately I'm not able to reproduce it and don't even know how the issue manifests itself - if the app freezes for a long time and if it occurs multiple times during one run of the app |
@JurajKuliska @connyduck Could you share an ANR report with the stacktrace from all threads like #1487 (comment) above? This way we can check if this is due to any activity OneSignal is running on other threads. |
@jkasten2 sure these are two different reports I was able to pull out from there... hope it helps |
@JurajKuliska Thanks for the logs. I see your app process was started by
however there isn't any OneSignal code running when the ANR happened. Your crash 123.txt looks like it happens when your app is resumed and I see Both your reports ANR reports have |
@JurajKuliska Did the above help with your issue? Either way let us know with any details you have. Thanks. |
@jkasten2 thanks for getting back to this. I've checked after a longer time and the issue hasn't appeared again in the last two months and even then it was on the older version of the sdk so I would consider this to be resolved (at least for us) |
@JurajKuliska Thanks for letting us know, and good to hear it seems to be fixed for you. Since a number of things have changed since the the original post I am closing this issue. However if the exact same ANR is happening feel free to reply here. However if the ANR is different in anyway please make a new issue, but feel free to refer to this one if you think it is related. |
Description:
We see a lot of ANRs reported through Google Play Console. Most of them do not have a stacktrace attached but the device information is very clear: >90% occur on Huawei devices running 8.
From the few stacktraces it looks like it could maybe be a bug in Google Cloud messaging?
Environment
OneSignal Gradle plugin 0.13.4
OneSignal 4.6.0
minSdk 21
targetSdk 30
Steps to Reproduce Issue:
Unfortunately I cannot reproduce this on any of my devices
Anything else:
stacktrace from a Samsung Galaxy A41 running Android 11
Please let me know if you need more information
The text was updated successfully, but these errors were encountered: