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

Hi. We are also experiencing the same behavior since several days ago.
Our business model requires a higher traffic during this time of month, which is why we have seen the err - maybe the error appeared even before.

If the user re-tries ( using the same credentials ) the same action couple of minutes after , it is working.

Please advice.

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

Hello,

As the example shown in the video is testing the connection multiple times in a row, has it happened by testing the connection once (or until it succeeds), then running the code and queries needed and after a while trying to connect again? Is it still failing?

Regards.

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

hi. it is happening randomly. the user uses the same credentials and same scenario each time.
We have also noticed that sometimes if we refresh the Google Sheet file, from where the INSERT is fired , using the JDBC connection , we are able to connect and insert the records.

Last year we have had a similar issue due to a rollout of some changes on JDBC class ( related to Issue # 28402227 )
Following the discussions with your developers , they did a rollback which fixed the error and we were able again to use the mechanism.
I guess now there is another rollout related to JDBC ?
Or what is the reason of this issue happening suddenly and randomly?

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

I have the same problem, since in this last month my script is executed by many users.

It connects intermittently and when it doesn't, it stays 30 seconds connecting until the error is thrown.

I tell my users to try to run the code over and over again, until they finally connect.

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