Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

Two splash screens show one after the other when the app starts

ErrorPlay Console pre-launch warning: Double splash screen

Short 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.

  • Applies to Android 12 to 15, androidx.core:core-splashscreen 1.2.0, Android Studio
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 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*/
  2. 2Match what you see, then jump to its fix

    1. 1Two splashes in a row on Android 12 and later, one on older versionsA dedicated splash Activity runs after the system splashFix
    2. 2Your branded background no longer shows on Android 12+A custom windowBackground splash is replaced by the system oneFix
    3. 3The splash disappears, then an empty screen shows while data loadsData loading after the first frame makes a second blank screenFix

What does the error look like?

  • Play Console pre-launch warning: Double splash screen
  • The 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.xml

2Fix

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 icon

Confirmed by developer.android.com

Did this fix it?

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

Did this fix it?

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 onCreate

2Fix

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 launch

Confirmed by developer.android.com

Did this fix it?

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

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 fix

Mobile 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

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.