[cfw] "No ViewModelStoreOwner was provided via LocalViewModelStoreOwner"

[jershell]

Unable to use the lifecycle-viewmodel-compose with web target

Describe the bug "No ViewModelStoreOwner was provided via LocalViewModelStoreOwner"

Affected platforms

• Web (K/JS) - Canvas based API

Versions

• Kotlin version*: 1.9.23
• Compose Multiplatform version*: 1.6.10-beta01, 1.6.10-dev1599
• Lifecycle-viewmodel-compose*: 2.8.0-alpha01
• OS version(s)* (required for Desktop and iOS issues): Ubuntu 22.04.3
• OS architecture (x86 or arm64): x86_64
• Device (model or simulator for iOS issues): Chrome 123.0.63
• JDK (for desktop issues): Temurin 17

To Reproduce Steps and/or the code snippet to reproduce the behavior:

1. Go to web
2. Open console
3. See error

Expected behavior Label with current time on screen

Source code

• https://github.com/jershell/web-kmp-mvvm/blob/main/composeApp/src/commonMain/kotlin/com/github/jershell/containers/foobar/FooBar.kt#L24
• https://github.com/jershell/web-kmp-mvvm/

[kropp]

Hi @jershell please update to the just released 1.6.0-beta02 and change the line viewModelFactory { FooBarViewModel() } to viewModelFactory { initializer { FooBarViewModel() } } That should fix the issue.

[pablichjenkov]

Is this initializer {} block, the API moving forward for all platforms? It really doesn't look appealing having these 2 inner blocks with an almost equal semantic name, ViewModelFactory and initializer.

[jershell]

Hi @jershell please update to the just released 1.6.0-beta02 and change the line viewModelFactory { FooBarViewModel() } to viewModelFactory { initializer { FooBarViewModel() } } That should fix the issue.

Hi. I up version. Viewmodel is working. Thanks you!

[MatkovIvan]

Is this initializer {} block, the API moving forward for all platforms?

It's the API from Android/Google, not new one. There is another overload with trailing lambda, so the usual syntax will be like:

viewModel { FooBarViewModel() }

As for "2 inner blocks": One factory might contain multiple initializers for different types. It's useful if you want to create a single factory for all your ViewModel types instead of separate ones for each viewModel call

[pablichjenkov]

Wow 😲 I never used it TBH. Thanks

[okushnikov]

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.