windowSplashScreenBrandingImage missing from SplashScreen [194301890]

Assigned

Feature Request

core-splashscreen

Status Update

No update yet.

Description

sc...@gmail.com

created issue #1

Jul 22, 2021 11:13AM

Component used: core-splashscreen Version used: 1.0.0 Devices/Android versions reproduced on: Samsung S10, Android 11

I'm trying to create a backwards compatible splash screen, I understand that from this documentation that:

Prior API 31, the platform behavior is replicated with the exception of the Animated Vector Drawable support on the launch screen.

However I don't seem to be able to use windowSplashScreenBrandingImage either as it's missing from the attrs file in the core-splashscreen library. Is this something that can be introduced in an update to the splashscreen library or will it also be unsupported pre-31?

Comments

al...@google.com <al...@google.com> Jul 27, 2021 02:34PM

Reassigned to ca...@google.com.

ca...@google.com <ca...@google.com> #2Aug 2, 2021 12:20PM

The design guideline is to avoid using the branding image so it's a low priority for the compat lib

da...@gmail.com <da...@gmail.com> #3Oct 8, 2021 12:13PM

If you want to change the look of your splash screen across all android API > 21 how can you offer a feature (windowSplashScreenBrandingImage) in the latest 31 version only and not in the app compat lib. windowSplashScreenBrandingImage can be quite useful for some legacy custom splash screen elements replacement.

Message last modified on Oct 8, 2021 02:36PM

gs...@gmail.com <gs...@gmail.com> #4Oct 18, 2021 01:04PM

Also from the docs:

After you migrate using the SplashScreen compat library, the system displays the same splash screen on all versions of Android.

Message last modified on Oct 18, 2021 07:21PM

we...@gmail.com <we...@gmail.com> #5Oct 19, 2021 10:08AM

Really need windowSplashScreenBrandingImage because my old spalsh screen has this element.

ju...@gmail.com <ju...@gmail.com> #6Sep 22, 2022 09:59AM

Any update on this ? I also really need windowSplashScreenBrandingImage for migrating my old splash screen.
As said above this is supposed to be available in the SplashScreen compat api as it claims that it renders the same on all versions of Android.
IMHO this ticket should be a bug like 204364858, not a feature.

ca...@google.com <ca...@google.com> Sep 22, 2022 10:08AM

Reassigned to wi...@google.com.

wi...@google.com <wi...@google.com> #7Sep 22, 2022 01:34PM

I am afraid that we cannot support the windowSplashScreenBrandingImage for API < 31.

The position of branding image can be adjusting based on the display size, for example, framework will decide to not show it if there doesn't have enough space on the screen for it, so those calculation need to happen at runtime.

For API < 31 device, the support library will draw the icon on the splash screen window, however, and it can only support for static layout since at that time framework does not support this feature. If we want to support this attribute and force it to show at a specific position, user may saw it overlays the icon or out of screen on a small device.

If the branding image is really important, consider to use the attribute windowBackground for API <31 device.

wi...@google.com <wi...@google.com> #8Sep 23, 2022 01:32AM

Per-talk, @caen suggest we can use smallestWidth to avoid the potential issue on comment#7.

ar...@gmail.com <ar...@gmail.com> #9Nov 2, 2022 10:37PM

As of November 2 2022 .. windowSplashScreenBrandingImage seems still not be back-ported but the Play Store requires us to target the new API's. I think this might need some action :-).

ca...@digitalchargingsolutions.com <ca...@digitalchargingsolutions.com> #10Nov 17, 2022 11:57AM

So reading #7 this seems to be a wontfix, but it's still assigned? Can you please clarify this?

Even with the reasoning of "we can't backport it", the attr "windowSplashScreenBrandingImage" should still be available at the compat library, especially as the docs say "but we strongly recommend using the Androidx SplashScreen compat library instead."

Message last modified on Nov 17, 2022 12:08PM

wi...@google.com <wi...@google.com> #11Nov 17, 2022 12:19PM

we should fix it, but haven't find time to do that.

su...@fisglobal.com <su...@fisglobal.com> #12Jan 20, 2023 01:15PM

Android has now made Splash screen mandatory and this is required for migrating existing apps. Can you please let us know when would this be fixed?

ca...@digitalchargingsolutions.com <ca...@digitalchargingsolutions.com> #13Mar 14, 2023 01:43PM

Bump, it would be nice to have this worked on...

ki...@protonmail.com <ki...@protonmail.com> #14Mar 24, 2023 05:20PM

It would be great to fix this issue, it's been 3 years :)

af...@vexiza.com <af...@vexiza.com> #15Apr 4, 2023 12:57PM

Is there an expected date when the problem will be fixed?

Since the inclusion of the SplashScreen is mandatory, and not being able to use a brand image... this limits the functionality that we had previously.
We have to implement actions not recommended in the documentation, such as having the SplashScreen and having a custom screen as well. No sense...

wi...@google.com <wi...@google.com> Apr 14, 2023 02:17AM

Reassigned to rg...@google.com.

es...@oracle.com <es...@oracle.com> #16Apr 29, 2023 02:09AM

Is there a date or timeframe when this fix will be implemented?

ca...@digitalchargingsolutions.com <ca...@digitalchargingsolutions.com> #17Aug 5, 2023 07:12AM

Unfortunately the Splash Screen APIs (& the compat lib) are becoming a meme in the Android dev community...

It's strongly suggested we use this lib and then Google basically treats it as feature complete or deprecated (depends on how you see it) without ever having feature completed it. I don't want to only be negative, so hey, I and others would be happy if this would be improved :).

Message last modified on Aug 5, 2023 07:12AM

fa...@gmail.com <fa...@gmail.com> #18Nov 17, 2023 09:24AM

For version 11 and earlier "android:windowBackground" is available, I tested it and it works fine.

jo...@gmail.com <jo...@gmail.com> #19Feb 27, 2024 08:59AM

I'm using windowBackground as a fallback as comment#18 mentioned, but don't know how to get the exact corner radius value of logo from the system like ?android:actionBarSize.