RemoteServiceException: Bad notification posted on Marshmallow Coolpad devices |
||||
Issue descriptione.g. Bad notification posted from package com.android.chrome: Couldn't update icon: StatusBarIcon(icon=Icon(typ=RESOURCE pkg=com.android.chrome id=0x00000000) visible user=0 ) at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1536 ) at android.os.Handler.dispatchMessage (Handler.java:102 ) at android.os.Looper.loop (Looper.java:148 ) at android.app.ActivityThread.main (ActivityThread.java:5609 ) at java.lang.reflect.Method.invoke (Native Method ) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:797 ) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:687 ) We already disabled badges for Samsung Marshmallow devices at Issue 829367 , we may need to do the same for Coolpad Marshmallow devices too, but worth repro-ing and proving the fix on a device first. (Also need to check what Build.MANUFACTURER reports on one of these devices to put in the device-specific fallback) Crash link (includes Samsung devices too): https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27%20AND%20%20expanded_custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BAndroid%20Java%20Exception%5D%20android.app.RemoteServiceException%20at%20android.app.ActivityThread%24H.handleMessage(ActivityThread.java)%27%20AND%20EXISTS%20(SELECT%201%20FROM%20UNNEST(thread)%20WHERE%20StackTrace.error_message%3D%27Bad%20notification%20posted%20from%20package%20com.android.chrome%3A%20Couldn%5C%27t%20update%20icon%3A%20StatusBarIcon(icon%3DIcon(typ%3DRESOURCE%20pkg%3Dcom.android.chrome%20id%3D0x00000000)%20visible%20user%3D0%20)%27)%20AND%20expanded_custom_data.ChromeCrashProto.channel%3D%27stable%27
,
Apr 10 2018
,
Apr 10 2018
,
Apr 25 2018
The NextAction date has arrived: 2018-04-25
,
Apr 27 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/463b699604bbc16c1e3b29e4a60dce9c6cbe1fdd commit 463b699604bbc16c1e3b29e4a60dce9c6cbe1fdd Author: Anita Woodruff <awdf@chromium.org> Date: Fri Apr 27 18:34:17 2018 [Android] Disable custom status bar notification icons on M Coolpads - Use the fallback Chrome logo instead of attempting to set a custom badge as the status bar icon for all web notifications on Marshmallow Coolpad devices, same as what we do on Samsung Marshmallow devices, to avoid a crash. - Tested with a Coolpad 3600i (the model experiencing most of the non-Samsung crashes) which reports its Build.MANUFACTURER to be 'YuLong'. R=nyquist@chromium.org Bug: 831220 Change-Id: Id475bbda198c7c61fbb4d114bb562826ffd351e5 Reviewed-on: https://chromium-review.googlesource.com/1028271 Reviewed-by: Tommy Nyquist <nyquist@chromium.org> Commit-Queue: Anita Woodruff <awdf@chromium.org> Cr-Commit-Position: refs/heads/master@{#554428} [modify] https://crrev.com/463b699604bbc16c1e3b29e4a60dce9c6cbe1fdd/chrome/android/java/src/org/chromium/chrome/browser/notifications/NotificationBuilderBase.java [modify] https://crrev.com/463b699604bbc16c1e3b29e4a60dce9c6cbe1fdd/chrome/android/javatests/src/org/chromium/chrome/browser/notifications/StandardNotificationBuilderTest.java
,
May 2 2018
Thanks for this fix Anita! Are there any other next actions here or can we mark this fixed now?
,
May 2 2018
Should be fixed :) Haven't yet seen any more of these kinds of crashes in the releases which have contained this fix & the Samsung fix, which is encouraging: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27+AND++expanded_custom_data.ChromeCrashProto.ptype%3D%27browser%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BAndroid+Java+Exception%5D+android.app.RemoteServiceException+at+android.app.ActivityThread%24H.handleMessage%28ActivityThread.java%29%27+AND+EXISTS+%28SELECT+1+FROM+UNNEST%28thread%29+WHERE+REGEXP_CONTAINS%28StackTrace.error_message%2C+%27Bad+notification+posted+from+package+.*%3A+Couldn%5C%27t+update+icon%3A+StatusBarIcon%27%29%29+AND+REGEXP_CONTAINS%28product.Version%2C+%22%5E%2867.0.339%283%7C6%29%7C68%29%22%29 The reduction in crashes should be more obvious once 67 rolls to beta & stable though. |
||||
►
Sign in to add a comment |
||||
Comment 1 by awdf@chromium.org
, Apr 10 2018