Two splash screens show one after the other when the app starts
Play Console pre-launch warning: Double splash screenShort answer
Since Android 12 the system draws a splash screen on every cold or warm start. If your app also has a splash activity, users see two. Migrate to the SplashScreen compat library: add a Theme.SplashScreen theme, call installSplashScreen() before super.onCreate(), and remove or hold back the old splash activity.
Fix it fast
1Find out which cause you have
Find out how the old splash is built: a dedicated activity, or a theme with windowBackground. The fix differs for each.
grep -rn "Splash" app/src/main/AndroidManifest.xml app/src/main/res/values*/2Match what you see, then jump to its fix
- 1
Two splashes in a row on Android 12 and later, one on older versionsA dedicated splash Activity runs after the system splashFix - 2
Your branded background no longer shows on Android 12+A custom windowBackground splash is replaced by the system oneFix - 3
The splash disappears, then an empty screen shows while data loadsData loading after the first frame makes a second blank screenFix
- 1
What does the error look like?
Play Console pre-launch warning: Double splash screenThe system splash shows, followed by your existing splash screen activity
Cause 1 of 3
A dedicated splash Activity runs after the system splash
1Check
The launcher activity in the manifest is a splash or routing activity.
grep -n -B2 -A6 "LAUNCHER" app/src/main/AndroidManifest.xml2Fix
Migrate to the SplashScreen API. If that activity only routes, keep it but hold back its drawing so the splash carries over to the next activity; better, remove it and link directly to the real activity.
class RoutingActivity : ComponentActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
val splashScreen = installSplashScreen()
super.onCreate(savedInstanceState)
splashScreen.setKeepOnScreenCondition { true }
startActivity(Intent(this, MainActivity::class.java))
finish()
}
}3Verify
Cold-start the app on an Android 12+ device: one splash, then the main screen.
# Close the app from recents, then tap its launcher iconConfirmed by developer.android.com
Cause 2 of 3
A custom windowBackground splash is replaced by the system one
1Check
Look for a launch theme that sets android:windowBackground to a drawable.
grep -rn "windowBackground" app/src/main/res/2Fix
Create a theme with parent Theme.SplashScreen, set windowSplashScreenAnimatedIcon and postSplashScreenTheme, use it in the manifest, and call installSplashScreen() before super.onCreate().
<style name="Theme.App.Starting" parent="Theme.SplashScreen">
<item name="windowSplashScreenBackground">@color/splash_bg</item>
<item name="windowSplashScreenAnimatedIcon">@drawable/splash_icon</item>
<item name="postSplashScreenTheme">@style/Theme.App</item>
</style>3Verify
The launch shows your colour and icon on every Android version.
// MainActivity.onCreate
installSplashScreen()
super.onCreate(savedInstanceState)Confirmed by developer.android.com
Cause 3 of 3
Data loading after the first frame makes a second blank screen
1Check
The splash is dismissed as soon as the app draws its first frame.
# Look for async loading in the first activity's onCreate2Fix
For a small local load, keep the splash up with setKeepOnScreenCondition. For network loads, dismiss the splash and show placeholders.
val splashScreen = installSplashScreen()
super.onCreate(savedInstanceState)
splashScreen.setKeepOnScreenCondition { !viewModel.isReady.value }3Verify
The splash stays until content is ready, then the content appears.
# One continuous launchConfirmed by developer.android.com
How do I stop it coming back?
- Use the SplashScreen compat library (core-splashscreen) for every launch theme.
- Do not use a splash activity for branding or routing.
- Keep Application.onCreate() light so no splash has to wait.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
Related fixes
Mobile apps
adb cannot start because something already holds its port
adb start-server failed
The adb server must bind local TCP port 5037, and every adb client talks to it there.
2 causes, each with a fixMobile apps
The phone shows as unauthorized and Android Studio will not run the app
adb devices lists the phone but Android Studio cannot deploy to it
An unauthorized phone means it has not trusted this computer's RSA key.
3 causes, each with a fixMobile apps
Android Studio cannot pair the phone over Wi-Fi
The Pair devices over Wi-Fi dialog lists no device
Wireless pairing needs the phone on Android 11 or higher and on the same Wi-Fi network as the computer, with current Platform-Tools.
4 causes, each with a fixMobile apps
adb cannot connect to its daemon or start the server
* daemon started successfully *
The adb server is a background process on your computer that listens on TCP port 5037.
2 causes, each with a fixMobile apps
adb prints 'server version doesn't match this client; killing...'
adb server version doesn't match this client; killing...
adb runs a background server, and every adb command is a client.
3 causes, each with a fixMobile apps
adb tcpip 5555 fails because no device is found
adb: more than one device/emulator
adb tcpip only works while the device is attached and listed by adb, because it tells the phone to start listening on port 5555.
4 causes, each with a fix