
On iOS, passkeys are controlled by a build flag. Today there is also a feature flag that controls a subset of passkey functionality, but it is redundant and having its state inconsistent with the build flag could cause bad behavior. This CL: * Exposes the passkey build flag as a header on iOS * Adds a new helper function to check enabled/disabled status, which passes through our build flag value on iOS, the feature flag value on desktop, and false on Android (where the flag never existed). * Replaces direct references to the feature flag in the iOS build tree with references to the new helper function * Disables some tests on iOS temporarily. We intend to flip the build flag within the next few days, which will reenable these tests. Further references (sorry, Googlers only): go/bling-passkeys go/bling-passkeys-launch-plan Change-Id: I712d4674604642753c1086bd20aed1f45eeed9e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5933709 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Alexis Hétu <sugoi@chromium.org> Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by: Rushan Suleymanov <rushans@google.com> Commit-Queue: Tommy Martino <tmartino@chromium.org> Cr-Commit-Position: refs/heads/main@{#1374015}
See components/sync/README.md.