Repository navigation
PHO-91/#184: Build against Compose Multiplatform 1.10.1 and lifecycle 2.9.6 - #185
Merged
wow-miley merged 1 commit intoOct 20, 2026
Conversation
… 2.9.6 phosphor-lumos-surface 0.9.0, built on Compose 1.7.0, reads ProvidedValue$stableprop directly in its Native klib. Compose 1.10 made that property private behind a _getter, so Socket's iOS app (Compose 1.10.1) threw IrLinkageError the first time LumosSurface composed. Building on 1.10.1 makes the compose compiler go through the getter. lifecycle-runtime-compose moves to 2.9.6, the version Compose 1.10.1's ui module requires. No source changes were needed; the yarn lockfiles regenerate unchanged. Authored by Claude (Opus 5.5), not by the committer. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
wow-miley
deleted the
miley/pho-91-build-against-compose-multiplatform-1101-phosphor-lumos
branch
October 20, 2026 21:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #184
What was wrong
Phosphor built against Compose Multiplatform 1.7.0. In the Native klib of
phosphor-lumos-surface0.9.0, the compose compiler readandroidx_compose_runtime_ProvidedValue$stablepropdirectly, forCompositionLocalProvider(LocalLumosSurfaceState provides state). Compose 1.10 makes that property private and exposes$stableprop_getterin its place. So Socket's iOS app, which links Compose 1.10.1, threwIrLinkageErrorthe first time aLumosSurfacecomposed.Change
settings.gradle.kts:org.jetbrains.composegoes from 1.7.0 to 1.10.1, the version Socket and ampere-core build against.phosphor-lumos-composeandphosphor-lumos-surface:lifecycle-runtime-composegoes from 2.8.3 to 2.9.6, whichorg.jetbrains.compose.ui:ui:1.10.1's.modulerequires. The comments beside it are updated to match.kotlin-js-store/: I rankotlinUpgradeYarnLockandkotlinWasmUpgradeYarnLock, and both lockfiles came out unchanged.Deviations from the ticket
v0.9.0) is left to Miley, as the ticket says.Verification
Local:
:phosphor-lumos-compose:jvmTest,:phosphor-lumos-surface:jvmTest(including theImageComposeScenetests),:phosphor-lumos-compose:compileKotlinIosSimulatorArm64and:phosphor-lumos-surface:compileKotlinIosSimulatorArm64all passed with no warnings.$stablepropreads prints nothing for either module. The surface klib now carriesandroidx_compose_runtime_ProvidedValue$stableprop_getterinstead.Left to CI:
.modulelocally, because the machine's build slot was busy.compose.runtime,compose.uiandcompose.foundationresolve to the plugin version, so they should now require 1.10.1.Still owed by a person: the release, then Socket's SCKT-912 bump and an on-device check of the iOS flights.
Authored by Claude (Opus 5.5), not by the committer.
🤖 Generated with Claude Code