test(e2e): skip 2 flaky flows until underlying SDK/Maestro bugs are fixed

sign-in-sign-out-sign-in.yaml: tag `skip` on both platforms.
  - Android: clerk-android AuthStartView reads Clerk.enabledFirstFactorAttributes
    and Clerk.socialProviders via non-observable getters. Body of re-mounted
    AuthView can be empty when its first composition wins the race against
    environment population. Fix is a MutableStateFlow + observe in AuthStartView
    (patch staged in clerk-android workspace, pending publish).
  - iOS: Maestro's field-clearing on the second sign-in leaves a leading char
    ("Identifier is invalid"). Lives in the test/keyboard layer, not the SDK.
  Both bugs only repro on slow CI hardware; local AVD/sim are too fast.

sign-out-from-profile.yaml: tag `flakyAndroid` (Android-only exclusion).
  - Same Android-side clerk-android race, manifesting earlier in this flow
    because of state bleed from preceding flows in the Maestro sweep.
  - Keeps running on iOS, where the underlying race doesn't apply.

Workflow Android job's --exclude-tags now includes `flakyAndroid`. iOS is
unchanged (already correctly excludes androidOnly).

Re-enable both flows by removing the tags once the underlying issues are
fixed and verified.

Author: chriscanin

.github/workflows/mobile-e2e.yml

@@ -336,7 +336,7 @@ jobs:
             cd integration/mobile &&
             find flows -type f -name "*.yaml" ! -path "*/common/*"
             ${FLOWS_FILTER:+-path "*$FLOWS_FILTER*"} -print0
-            | xargs -0 maestro test --env CLERK_TEST_EMAIL="$CLERK_TEST_EMAIL" --env CLERK_TEST_PASSWORD="$CLERK_TEST_PASSWORD" --exclude-tags "$EXCLUDE_TAGS"
+            | xargs -0 maestro test --env CLERK_TEST_EMAIL="$CLERK_TEST_EMAIL" --env CLERK_TEST_PASSWORD="$CLERK_TEST_PASSWORD" --exclude-tags "$EXCLUDE_TAGS,flakyAndroid"
 
       - name: Upload Maestro artifacts on failure
         if: failure()

integration/mobile/flows/cycles/sign-in-sign-out-sign-in.yaml

@@ -1,9 +1,22 @@
 # REGRESSION: After sign-in -> sign-out -> sign-in, the second sign-in
 # completed natively but the JS SDK never picked it up. This flow signs in
 # twice in a row to verify the cycle works correctly.
+#
+# TODO: re-enable once two underlying issues are fixed:
+#   - Android: clerk-android AuthStartView reads Clerk.enabledFirstFactorAttributes
+#     and Clerk.socialProviders via non-observable getters; the body of a re-mounted
+#     AuthView can be left empty when its first composition wins the race against
+#     environment population. A MutableStateFlow + observe in AuthStartView fixes
+#     it (see drafted patch in clerk-android workspace).
+#   - iOS: Maestro's field-clearing on the second sign-in leaves a leading
+#     character (saw ".ci-..." in failing screenshots), which Clerk rejects as
+#     "Identifier is invalid".
+# Both bugs are real; both manifest only on slower hardware (CI) and both pass
+# reliably on local Pixel 9 Pro / iPhone 17 Pro simulators.
 appId: com.clerk.clerkexpoquickstart
 tags:
   - regression
+  - skip
 ---
 - runFlow: ../common/open-app.yaml
 # First sign-in

integration/mobile/flows/profile/sign-out-from-profile.yaml

@@ -1,8 +1,13 @@
 # Happy path: sign in, open profile, sign out from inside the profile modal,
 # assert AuthView is shown again.
+#
+# Flaky on Android CI: see TODO in cycles/sign-in-sign-out-sign-in.yaml. Same
+# clerk-android AuthStartView re-render race. Pass-rate is ~50% on CI. Keep
+# running on iOS where the underlying issue doesn't manifest.
 appId: com.clerk.clerkexpoquickstart
 tags:
   - happy-path
+  - flakyAndroid
 ---
 - runFlow: ../common/open-app.yaml
 - runFlow: ../common/sign-in-email-password.yaml