Infeasible
Status Update
No update yet.
Comments
ar...@google.com
Can you please capture a bug report and share it here. We need to analyze what is happening before this crash trace.
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
[Deleted User] <[Deleted User]>
I wish I could do that. I failed to reproduce this issue on my device, I only see them in our crash reporting solution.
ar...@google.com
Please provide the bug report requested in
ko...@gmail.com
There is an additional discussion about this crash:
https://github.com/OneSignal/OneSignal-Android-SDK/issues/263
I have got a lot of the same crashes but I can't reproduce this issue.
I have got a lot of the same crashes but I can't reproduce this issue.
bo...@gmail.com
Hello everyone, we are seeing the same crash on our app, although it seems that in a very small percentage it also happens on Android 6.0 devices. We also weren't able to reproduce the issue so the only reports we have are from the Google Play dashboard. I'll attach a screenshot of it. Please let us know if this issue is being handled or if you need any more information from our side(we will post a bug report if and when we'll be manage to reproduce the crash).
Thank you very much, Boby Ilea
Thank you very much, Boby Ilea
ar...@google.com
We are closing this issue as we don't have enough actionable information.
If you are still facing this problem, please open new issue and add the relevant information along with reference to earlier issue.
If you are still facing this problem, please open new issue and add the relevant information along with reference to earlier issue.
Description
Version used: 25.4.0
Theme used: Theme.AppCompat.Light.NoActionBar
Devices/Android versions reproduced on (sample from the last 90 days): Android 7.0 on SC-04J, HUAWEI NXT-L29, SM-G950U, SM-G950F, SM-G955U, SM-A510F, Moto G (5) Plus, SM-T817V, SM-G955F, VS500, XT1585, SM-G950W, SM-J327V, Moto G (4), SM-P580, XT1650.
After each release, we see crashes from several users with the stacktrace like this:
android.app.RemoteServiceException: Bad notification posted from package com.futuresimple.base: Couldn't expand RemoteViews for: StatusBarNotification(pkg=com.futuresimple.base user=UserHandle
{0}
id=1024 tag=null key=0|com.futuresimple.base|1024|null|10127: Notification(pri=0 contentView=null vibrate=null sound=null defaults=0x0 flags=0x10 color=0x00000000 vis=PRIVATE))
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1644)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6123)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:757)
The crash is always related to application update.
The crash seems to happen for all notifications issued by our application (i.e. there are different notification ids in stacktraces, but they cover all frequently used notifications).
The only common thing is the OS version.
The crashes usually happen in "bursts", i.e. if the crash occurs, it is usually repeated several times for a given user.
Some users seem to be more affected than the others – we estimated the probability of crash occurrence at 1-2%, but after last 17 releases, one user was affected by this crash 9 times, which is highly unlikely.
I'll be happy to provide you with more information.