fix(build): restore theme switching by re-aligning the Compose stack (release 26.07.02)#98
Merged
Merged
Conversation
…(release 26.07.02) Lifecycle 2.11.0 (from the 26.07.01 dependency refresh) transitively pulls a newer androidx.compose.ui/runtime than composeBom 2024.12.01 pins, splitting the Compose stack across versions; preference-driven recomposition broke and theme selections persisted without repainting the app. Pin lifecycle back to 2.10.0 (the last BOM-aligned version), teach dependabot to hold androidx.lifecycle until it moves together with the Compose BOM, and cut 26.07.02. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016AYAgNYmBkxsEYcgzSAjgT
ErikChevalier
added a commit
that referenced
this pull request
Jul 3, 2026
Bump appVersionName (versionCode derives to 260702) and add the Material You auto-disable fix to the 26.07.02 CHANGELOG section alongside the Compose stack re-alignment from #98. Co-authored-by: FlintWave <flintwave@tuta.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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
2 participants
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.
What & why
Fixes the theme-switching regression reported on 26.07.01: selecting a theme (or light/dark/system mode) in the app's Settings persisted but never repainted the app.
Root cause: the 26.07.01 dependency refresh bumped AndroidX Lifecycle 2.10 → 2.11, which transitively pulls a newer
androidx.compose.ui/runtimethan the pinnedcomposeBom = 2024.12.01provides — splitting the Compose stack across versions (evidence: compose-ui's newLocalContextGetResourceValueCalllint rule appeared whileLocalResourcesdidn't exist yet at compile time). Cross-version Compose artifacts break preference-driven recomposition, which is exactly the theme picker's plumbing (collectAsStateWithLifecycle→SearchMobTheme). Nothing in the app's own theme code changed since 26.06.06.Changes:
lifecycleRuntimeKtx/lifecycleViewmodelComposeback to 2.10.0, the last version aligned with the BOM (the exact known-good matrix from 26.06.06), with a comment requiring the two to move only in lockstep withcomposeBom.ignoreforandroidx.lifecycle:*so the weekly minor-patch group can't silently reintroduce the skew; lifecycle 2.11+ should land together with a deliberate Compose BOM bump (2026.05.01 is available — see closed build: bump androidx.compose:compose-bom from 2024.12.01 to 2026.05.01 #9) and an on-device test.Relates to OpenSpec change: n/a (dependency regression fix)
Checklist
feat//fix/branch offmain./gradlew ktlintCheck lint test assembleDebugis green locally — verified by CI on this PR (this sandbox cannot run the Android toolchain)openspec validate <name> --strict) and tasks are checked off — n/a🤖 Generated with Claude Code
https://claude.ai/code/session_016AYAgNYmBkxsEYcgzSAjgT
Generated by Claude Code