The bump to 1.15.2 -- the release that carries the Marmot current profile -- breaks the compile in exactly two places, and the rest of the ~130 quartz symbols the app imports are untouched. CommitOrdering is gone from the library. Its inbound processor now settles same-epoch commits through a convergence engine and calls the old rule superseded "and deliberately": created_at and the event id are both transport metadata the sender chooses and MLS never authenticates, so a member could win every race by backdating. The app's pipeline does not go through that processor -- it drives MlsGroup itself -- so the rule is vendored unchanged into managers/CommitOrdering.kt, with a header saying why the library dropped it, until Phase 5 of docs/marmot-v2.md replaces the pipeline. NostrDao and MarmotInboundManager only change their import. GroupEventResult gained AppMessageOnCandidateBranch and RefusedByLifecycle, so the exhaustive when in ChatMessage.fromGroupEventResult needs both. Neither is a delivery -- the first is a payload that decrypted only on a losing fork, which the library is explicit must not be rendered, the second is input a disbanded or unrecoverable group refuses -- so both get no chat line, the same as a duplicate. The app never constructs either today. Verified rather than assumed: the two sources jars were diffed file by file against the app's imports; all 1,128 JVM tests pass on 1.15.2; the rewritten Curve25519 field arithmetic matches the RFC 8032 and RFC 7748 vectors bit for bit (the app persists raw MLS private keys, so this mattered); the app's own KeyPackages sit inside the new 84-day lifetime ceiling at 30 days; no new EventFactory kind collides with the app's. One-way door: MlsGroupState's blob goes from version 2 to version 4 and 1.14.0 has `require(version in 1..2)`, so a room re-persisted under this build cannot be opened by the previous one again. 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…