Skip to content

feat(core): the new core is the bridges' only: apps no longer pick it through Rees46Config, Flutter and React Native start it with Rees46.initializeBridge - #237

Merged
Xyzcancer merged 1 commit into
masterfrom
feat/bridge-only-core
Nov 17, 2026
Merged

Xyzcancer merged 1 commit into
masterfrom
feat/bridge-only-core

Conversation

@Xyzcancer

Copy link
Copy Markdown
Contributor

Apps can no longer pick the new core: Rees46Config loses coreV2 from its public init (code that passes it stops compiling), so Rees46.initialize and register run the old core.

Bridges start a shop on the new core with Rees46.initializeBridge(config, segment:, completion:) behind @_spi(Bridge), the same name as on Android. segment is the A/B group the bridge kept from its own storage. The device takes it only while it has no group of its own, and only A or B; otherwise the log says invalid_config with segment_kept or segment_invalid.

The core is still decided once per process by the first initialization.

… through Rees46Config, Flutter and React Native start it with Rees46.initializeBridge

Rees46Config no longer takes coreV2 in its public init, and the property is
internal: a configuration an app makes runs the old core. The bridges call
Rees46.initializeBridge(_:segment:completion:) behind @_spi(Bridge), which is
Rees46.initialize on the new core. The core is still decided once per process
by its first initialization, and core_flag_mismatch says so.

segment is the A/B group a bridge kept in its own storage. The device takes it
only while it has no group of its own, in the device's store or in the shop's
partition, and only A or B; otherwise invalid_config says segment_kept or
segment_invalid.
@Xyzcancer
Xyzcancer merged commit f81afe2 into master Nov 17, 2026
5 of 6 checks passed
@Xyzcancer
Xyzcancer deleted the feat/bridge-only-core branch November 17, 2026 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant