Status Update
Comments
al...@google.com <al...@google.com>
wi...@google.com <wi...@google.com>
da...@gmail.com <da...@gmail.com> #2
Thank you for your feedback! We've revised the error message in
ch...@google.com <ch...@google.com>
ap...@google.com <ap...@google.com> #3
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Meerkat | 2024.3.1 Canary 6
- Android Gradle Plugin 8.9.0-alpha06
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
ch...@google.com <ch...@google.com>
pr...@google.com <pr...@google.com> #4
Ok🙂
ch...@beyls.net <ch...@beyls.net> #5
Tell me if I'm wrong but the OS uses the SplashScreen theme to initially load the vector drawable in the zygote process on API 23+, before the Activity is even launched. At that moment, AppCompat can't be used anyway, so the display would still be incorrect on API 23 if the VD is using features like gradients.
Description
Component used:
androidx.core.splashscreen.SplashScreen
Version used: 1.0.0 Devices/Android versions reproduced on: Android 5, Android 6SplashScreen.install
method callsandroid.content.Context.getDrawable
on API 21. It, in turn, callsandroid.graphics.drawable.VectorDrawable.inflate
instead ofVectorDrawableCompat.inflate
.VectorDrawable
does not support some features like gradients, what may lead to a crash (see:VectorDrawable
.Suggestion: At least enable the users of the library to use
VectorDrawableCompat
instead ofVectorDrawable
.