Fixed
Status Update
No update yet.
Comments
pa...@gmail.com
Crash statistics.
rm...@google.com
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
je...@google.com
le...@google.com
Would you be able to share the whole stacktrace?
pa...@gmail.com
Here it is
Fatal Exception: android.app.RemoteServiceException: Bad notification posted from package yo.app.free: Couldn't expand RemoteViews for: StatusBarNotification(pkg=yo.app.free user=UserHandle{0} id=30 tag=null score=10 key=0|yo.app.free|30|null|10108: Notification(pri=1 contentView=yo.app.free/0x7f0d0142 vibrate=null sound=null defaults=0x0 flags=0x2 color=0x00000000 category=status vis=PUBLIC))
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1526)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5466)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Fatal Exception: android.app.RemoteServiceException: Bad notification posted from package yo.app.free: Couldn't expand RemoteViews for: StatusBarNotification(pkg=yo.app.free user=UserHandle{0} id=30 tag=null score=10 key=0|yo.app.free|30|null|10108: Notification(pri=1 contentView=yo.app.free/0x7f0d0142 vibrate=null sound=null defaults=0x0 flags=0x2 color=0x00000000 category=status vis=PUBLIC))
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1526)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5466)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
le...@google.com
The "drawable/ic_settings_grey600_24dp" resource itself looks fine. It seems that what causes the issue is how it's being loaded.
The difference with "drawable/ic_yowindow" is that it comes in only density so the image is put in the base instead of the density split. It looks like some devices have issues loading resources from the split APKs in this case.
What would really help is if you had a small sample project (with source code) which reproduces the issue.
The difference with "drawable/ic_yowindow" is that it comes in only density so the image is put in the base instead of the density split. It looks like some devices have issues loading resources from the split APKs in this case.
What would really help is if you had a small sample project (with source code) which reproduces the issue.
le...@google.com
I suspect this is similar to https://b.corp.google.com/issues/119872129 and that Spark devices don't support splits because they have forked Android.
le...@google.com
I believe that the other Samsung devices have loaded the same custom ROM (similar to the Spark and OnePlusOne devices) that doesn't support splits.
It is unfortunate that they report running 6.0.1 while not having the same functionality as the AOSP platform on 6.0.1 (i.e. support for config splits). We don't have a way on our end to detect if it's a custom ROM or not, so I'll just exclude the Spark devices on 6.0.1 from receiving splits, but there's nothing we can do for the other devices.
Excluding the Spark devices from receiving splits should reduce drastically your number of crashes.
It is unfortunate that they report running 6.0.1 while not having the same functionality as the AOSP platform on 6.0.1 (i.e. support for config splits). We don't have a way on our end to detect if it's a custom ROM or not, so I'll just exclude the Spark devices on 6.0.1 from receiving splits, but there's nothing we can do for the other devices.
Excluding the Spark devices from receiving splits should reduce drastically your number of crashes.
pa...@gmail.com
On our end we are going to implement the workarounds proposed by "ca" from InstantBits.
inhttps://issuetracker.google.com/issues/119872129
Thank you for referring this bug.
I understand the underlying issue.
Thank you for excluding Spark devices from splits. This should help.
in
Thank you for referring this bug.
I understand the underlying issue.
Thank you for excluding Spark devices from splits. This should help.
Description
The crash is attached.
Most devices are by Wileyfox manufacturer.
However, there are 5 different models from Samsung, including these.
Galaxy Ace3
Galaxy A5
The crash doesn't happen when no App Bundle involved. The app runs just fine on problem devices.
The layout file is attached.
When I remove this ImageView tag, the crash doesn't happen anymore to the user.
<ImageView
android:src="@drawable/ic_settings_grey600_24dp"
android:layout_width="16dp"
android:layout_height="16dp" />
It looks like there's something wrong with ic_settings_grey600_24dp image.
I have attached a .zip file with with source images for all the densities.
Probably the .png file compression on App Bundle side interferes.
The image is grayscale.
.png compressor can take advantage of this.
But Android 6.0.1 is probably not aware for this type of .png compression.
Pay attention that there's another .png file in the layout.
A colored image ic_yowindow (attached).
ic_yowindow displayed just fine on user's device with no crash.
If you need more details I'll be happy to assist.
I hope it won't take long to solve this mystery.
Pavel Repkin
YoWindow Weather app.