Every step a session takes is driven by a message arriving, and a device killed part way through its own pass is waiting on one that has already been delivered. The signer set is recorded, so it will never be processed again; the partial signature it would have produced was never made. The coordinator asking again cannot reach past it either -- what a resend asks a member for is the message this device believes it already sent -- so the session is a dead end on both sides, and in a room with several open proposals it is the one that was mid-pass that stops. So one sweep that no message drives: on opening a room, every session in it that is not settled and whose owner has answered is handed to `advance`, which does what it always does. It publishes nothing new -- each step asks whether its output exists rather than whether a stage says it ran -- and only answered sessions are passed in, so the approval gate is not approached, let alone reached past. A refusal counts as an answer for the same reason: a device killed between deciding and publishing says it on the next open rather than never. 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…