You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The splash screens show only the background color specified in the config.xml but not the drawable vector icon. This scenario occurs only the FIRST time (after the installation). Once the app is being opened once, after having close it, the icon is showed at each opening.
If can help, deploying directly from the Android studio (using version Iguana | 2023.2.1 Patch) the icon splash screen works like a sharm - so no issue. The problem appear only after having build the app and publish to our OTA (with same code obviously).
I would suggest raising the issue on google's issue tracker if you're encountering on Android 13 or later. Maybe it's a regression. Be prepared to provide a sample application.
This was a known issue for Android 12 or any earlier version which used the compatibility library and was supposedly fixed in Android 13 based on a google issue ticket which I can no longer find.
The splashscreen is entirely powered by Android SDK now, so I don't think there is anything that Cordova can do.
Bug Report
Problem
What is expected to happen?
Icon should be visible at each start up.
What does actually happen?
The splash screens show only the background color specified in the config.xml but not the drawable vector icon. This scenario occurs only the FIRST time (after the installation). Once the app is being opened once, after having close it, the icon is showed at each opening.
Information
Here below my config.xml
`
`
Command or Code
If can help, deploying directly from the Android studio (using version Iguana | 2023.2.1 Patch) the icon splash screen works like a sharm - so no issue. The problem appear only after having build the app and publish to our OTA (with same code obviously).
Environment, Platform, Device
i'm using for test purpose:
Version information
Checklist
The text was updated successfully, but these errors were encountered: