android 12 showing app icon and not image

[Roee-Tsur]

Hey,
I'm testing on a pixel 6 (android 12), when I start my app I see the app icon (currently default flutter icon) and not the asset I added.
I tested on android 11 emulator and it showed the right splash screen.

Since I'm using a pixel I guess it uses a google laucher so that shouldn't be a problem.

Can you help me solve this, please? I've been stuck for days.

this is my pubspec setup:
color: "#5bdabe"
color_dark: "#5bdabe"
image: assets/splash_logo.png
image_dark: assets/splash_logo.png
android12:
image_dark: assets/splash_logo.png
image: assets/splash_logo.png

[jonbhanson]

Did you see this note in the readme:

PLEASE NOTE: The splash screen may not appear when you launch the app from Android Studio. However, it should appear when you launch by clicking on the launch icon in Android.

[Roee-Tsur]

I know about this issue, I'm testing it by launching the app from the icon

…

On Tue, Jul 26, 2022, 19:48 Jon Hanson ***@***.***> wrote: Did you see this note in the readme: PLEASE NOTE: The splash screen may not appear when you launch the app from Android Studio. However, it should appear when you launch by clicking on the launch icon in Android. — Reply to this email directly, view it on GitHub <#400 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMNWOULJDHHNBIWSC7LRZYDVWAJEDANCNFSM54TTIE3A> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jonbhanson]

Your config should have an android_12 section, not an android12 section.

[elliotrtd]

@jonbhanson This may be related to the dark mode settings.

In my app android_12 was NOT taking the value for image when in dark mode when image_dark was not defined. I had to force image_dark to use the same value, this was easily missed in another app and it was only whilst testing this one with dark mode left on I found the problem.

[patrick-enzo]

@elliotrtd I also experienced this issue. The fix you mentioned worked for us as well.

[jonbhanson]

Thanks @elliotrtd for the heads up on this issue. I will push out an update that addresses this.