Repository navigation
Conversation
This branch has not been deployed
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.
Why
Draft pending the implementation merge and final behavior check. Secure Enclave enrollment remains behind the disabled-by-default
backup_enable_secure_enclave_sync_factorgate. Keep this PR as a draft and merge it whenbackup_enable_secure_enclave_sync_factoris turned on for production rollout, after checking the text against the final merged iOS implementation.Eligible iOS Sync Factors move to device-only Secure Enclave storage. The docs currently describe only non-synchronized Keychain storage and omit the pending-key registration lifecycle.
Tracks MCORE-2048. Implementation: worldcoin/world-app-ios#8681, reviewed at
71395239f0a5a8f073f3349e5e1d0aad793132c8.What
Factor permissions, backup encryption and format, Main Factor ceremonies, and Money/World ID sharing are unchanged by the implementation. Separate client authorization is tracked in MCORE-2045.
Test
71395239f0a5a8f073f3349e5e1d0aad793132c8.pnpm run spellcheck: passed.pnpm run check-links: passed.pnpm exec mint validate --telemetry false: passed; reported the pre-existing missingimages/favicon.svgreferenced by unchangeddocs.json.git diff --check: passed.make swiftlint-changedin the implementation evidence checkout: no changed Swift files.Risk
Documentation only. The text describes security-sensitive storage, enrollment, cleanup, and signing boundaries; it must be reviewed against the final merged iOS implementation before docs merge and broad rollout. Implementation PR #8681 is still open, so this is a draft pending that check. It does not introduce encrypted-archive replay or general resumable Turnkey account provisioning.