`lateinit property sessionParamsBuilder has not been initialized` when using compileSdk 33
See original GitHub issueI’m guessing that this might be due to a layoutlib incompatibility for compile sdk 33. SDK 32 works as expected.
kotlin.UninitializedPropertyAccessException: lateinit property sessionParamsBuilder has not been initialized
at app.cash.paparazzi.Paparazzi$Companion.getSessionParamsBuilder$paparazzi(Paparazzi.kt:612)
at app.cash.paparazzi.Paparazzi.prepare(Paparazzi.kt:161)
at app.cash.paparazzi.Paparazzi$apply$statement$1.evaluate(Paparazzi.kt:122)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at com.twitter.test.runner.TwitterTestRunner$1.schedule(TwitterTestRunner.java:61)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at org.junit.runners.Suite.runChild(Suite.java:128)
at org.junit.runners.Suite.runChild(Suite.java:27)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
Additional information:
- Paparazzi Version: 1.0.0
- Compile SDK: 33
- Gradle Version: 7.4.2
- Android Gradle Plugin Version: 7.2.1
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
lateinit property has not been initialized - Stack Overflow
I'm using the latest version of butterknife library. The following is my Kotlin class: class MenuItemView : LinearLayout { @BindView(R.id ...
Read more >You can check whether the lateinit property has been ... - Reddit
I would solely use this to test or debug "not initialized" errors that dont make sense to me. Leaving it in production code...
Read more >Initializing lazy and lateinit variables in Kotlin - LogRocket Blog
This article will explain how the lateinit modifier and lazy delegation can take care of unused or unnecessary early initializations.
Read more >Calling setIdentity in SFMCSdkReadyListener crashes with ...
UninitializedPropertyAccessException : lateinit property identity has not been initialized at com.salesforce.marketingcloud.sfmcsdk.SFMCSdk.
Read more >lateinit property _buildFeatureValues has not been initialized
When I want to convert a Kotlin library to Android library, I am getting this error. I only changed gradle of domain module....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This stack trace seems to happen whenever there’s any crashes in layoutlib’s setup. The issue you’re seeing may not be the same root cause as what I fixed in #487
Closing as resolved, per comment in https://github.com/cashapp/paparazzi/pull/487#issuecomment-1195584088