SplashScreen - lateinit property platformView has not been initialized [214835299]

Fixed

Bug

core-splashscreen

Status Update

No update yet.

Description

it...@gmail.com

created issue #1

Jan 18, 2022 07:51AM

Artifact used: androidx.core:core-splashscreen
Version used: 1.0.0-beta01
Theme used: Theme.SplashScreen
Crash Reproducible: False
Devices/Android versions reproduced on: Pixel 4a (5G) (Android 11)

A small number of users are affected by this crash (report via Crahlytics) & it seems to be very device-specific (mentioned above).

Stacktrace:

Caused by je.l: lateinit property platformView has not been initialized
       at androidx.core.splashscreen.SplashScreenViewProvider$ViewImpl31.getPlatformView(SplashScreenViewProvider.kt:119)
       at androidx.core.splashscreen.SplashScreenViewProvider$ViewImpl31.getSplashScreenView(SplashScreenViewProvider.kt:125)
       at androidx.core.splashscreen.SplashScreenViewProvider$ViewImpl31.getSplashScreenView(SplashScreenViewProvider.kt:117)
       at androidx.core.splashscreen.SplashScreenViewProvider.getView(SplashScreenViewProvider.java:62)
       at androidx.core.splashscreen.SplashScreen$Impl.setOnExitAnimationListener(SplashScreen.kt:308)
       at androidx.core.splashscreen.SplashScreen.setOnExitAnimationListener(SplashScreen.java:185)
       at com.domain.app.utils.extensions.MiscKt.handleSeamlessEnd(MiscKt.java:207)
       at com.domain.app.ui.activities.main.WhiplashActivity.onCreate(WhiplashActivity.kt:48)
       at android.app.Activity.performCreate(Activity.java:8036)
       at android.app.Activity.performCreate(Activity.java:8016)
       at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1329)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3581)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3765)
       at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:102)
       at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
       at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2193)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:201)
       at android.os.Looper.loop(Looper.java:288)
       at android.app.ActivityThread.main(ActivityThread.java:7796)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:974)

The handleSeamlessEnd extension method:

fun SplashScreen.handleSeamlessEnd() {
    setOnExitAnimationListener {
        it.iconView.animate()
            .alpha(1f)
            .setDuration(250L)
            .setListener(object : Animator.AnimatorListener {
                override fun onAnimationEnd(animator: Animator?) { it.remove() }
                override fun onAnimationStart(animator: Animator?) {}
                override fun onAnimationCancel(animator: Animator?) {}
                override fun onAnimationRepeat(animator: Animator?) {}
            })
    }
}

Comments

as...@google.com <as...@google.com> Jan 18, 2022 06:17PM

Assigned to ca...@google.com.

ca...@google.com <ca...@google.com> #2Jan 19, 2022 04:13PM

There is a report about it in kotlinlang Slack: https://kotlinlang.slack.com/archives/C01D6HTPATV/p1706005056105739

it...@gmail.com <it...@gmail.com> #3Jan 20, 2022 06:41AM

Thanks for the report!

ca...@google.com <ca...@google.com> #4Jan 20, 2022 10:09AM

The release notes documentation has been edited to clarify this change in behavior for line height.

To support non-standard text sizes, we encourage users to follow the Material design system and use a different type scale rather than changing the font size directly. Alternatively, users can overwrite the line height like so: style = LocalTextStyle.current.copy(lineHeight = TextUnit.Unspecified), or create a custom Typography entirely.

it...@gmail.com <it...@gmail.com> #5Jan 20, 2022 02:26PM

deleted

ca...@google.com <ca...@google.com> Jan 26, 2022 12:41PM

Marked as fixed.

ap...@google.com <ap...@google.com> #6Feb 1, 2022 04:57PM

In my case, I have multiple font sizes in the same Text (using SpanStyle in AnnotatedString). There are legitimate reasons for this. For example, when combining Chinese and English (phonetic) together (for language-learning purposes).