IssueTracker

AGP should migrate to the new API in KGP that allows lazy compiler plugin options specification. Since KGP 1.7.0 there is an API that can be used.

This issue will be fixed in AGP 7.4.0-beta03 and 8.0.0-alpha03.

Change: https://android.googlesource.com/platform/tools/base/+/b0f0b8c1de84edb328ae3a31769fa349e04e2be3

If you're never setting the content view, then setOnAnimationExitListener will never be called since your activity doesn't draw, so the splash screen isn't removed. In that case, just call call first handleRouting() and then installSplashScreen(). It should work like you intend.

That works. So I removed the setOnAnimationExitListener and called handleRouting() before installSplashScreen. The windowSplashScreenAnimatedIcon is shown when app is launched using the app launcher but not when started through the IDE, maybe that is intended as well?

Thanks for the clarification.

Yes it's intended because the IDE actually uses Instrumentation to open the app, so the system interprets that as one App opening another, and not the user clicking on the launcher icon

That's intended. By default it only show from the launcher. If the opening app wants to show the splash screen of the opened app, it needs to do:

Bundle options = ActivityOptions.makeBasic().toBundle() // or just new Bundle()
options.putInt("android.activity.splashScreenStyle", 1)
startActivity(intent, options)

Note that this is not an official API, but it works

On Android 12 the splash screen icon won't be shown from when launching from Studio and notification. For deep links it will depend on the browser behavior (see comment#8). When the splash screen icon isn't shown, the 'OnExitAnimationListener' won't be called

This is out of control for the library and will be changed for Android T.

I am currently keeping the splashScreen visible until login state has been checked, then I either remove it and show login or perform an animation on the splashScreenView icon before starting the next activity. I believe the solution mentioned above would not let my animation finish?

See my current code below, is there a way to identify when the 'OnExitAnimationListener' will not be called and just do the same stuff (minus animation) after the loading is done? Id didn't find a way for an activity to see what options it was launched with for getting the value of 'android.activity.splashScreenStyle'.

installSplashScreen().let { splashScreen ->
    splashScreen.setKeepOnScreenCondition {
        !isLoadingDone
    }
    splashScreen.setOnExitAnimationListener { splashScreenView ->
        if (isLoggedIn) {
            val animSet = createSplashIconAnimSet(splashScreenView)
            animSet.doOnEnd {
                startMainActivityAndFinish()
            }
            animSet.start()
        } else {
            splashScreenView.remove()
        }
    }
}

I would do something like this instead, where you keep the splash screen visible and handle the animation on your main activity:

LoginActivity:

onCreate() {
    val splashScreen = installSplashScreen()

    splashScreen.setKeepOnScreenCondition {
        !isLoadingDone
    }
    
    doLoadingStuff()....
}

fun doLoadingStuff() {
   ... 
   if(isLoggedIn) {
     startMainActivityAndFinish()
   } else {
     isLoadingDone = true
     // Splash Screen will be removed autmatically
   }
}

MainActivity:

 onCreate() {
    val splashScreen = installSplashScreen()
    splashScreen.setOnExitAnimationListener { splashScreenView ->
            val animSet = createSplashIconAnimSet(splashScreenView)
            animSet.start()

Yep. Cop out is accurate.

This is not working on Android 12 / 13 on prod builds and we are setting the content view.

This is a one-activity, full-compose app.

As a result our users on Samsung devices cannot get past our splash screen on Android 12 and 13.

A fix for this is necessary.

#4 was not even true, the setOnExitAnimationListener will still get called even when declared before setContentView. It's just that in Android 12 and 13 when the app was launched via IDE or instrumentation the setOnExitAnimationListener will never get called, the worst part of this is it doesn't happen on Android 14 and above. So always check your app against each of the Android version you are covering since the new Android teams like to deliver breaking changes feature with half-baked solution just like the new edge to edge enforcement.