In an expanded window the transcript beside the room list showed the first room opened and stayed there: pick another room and the list moved on while the pane did not. HomeScreen wraps the pane in key(chatRoomId), which rebuilds the composition when the selection changes, but viewModel() does not read composition keys. It scopes to the nearest ViewModelStoreOwner, and in the pane that is the home destination's one back stack entry for every room, so the second room's viewModel(factory = ...) got the first room's ChatRoomMessagingViewModel and ChatMessageListViewModel back with its factory ignored. A phone never showed it because a pushed room is its own entry with its own store. The pane now provides LocalViewModelStoreOwner with rememberViewModelStoreOwner() under the room key: a store per room, cleared when the selection moves on, and parked in the home entry's store so that it survives a rotation. Keying the two viewModel() calls on the room would have unstuck the pane too, at the price of keeping every room ever opened -- four DB collectors each -- in the home entry's store for as long as the home screen lives. ChatPaneSelectionJvmTest opens two rooms and comes back to the first, told apart by what was said in them since a name is on the row as well as the bar; its third case checks the room left behind stops collecting, which is the case the keyed alternative fails. The conformance doc's account of the hand-built pair records the trap. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform…