Repository navigation
test(expo): force-stop Google Play services when the Android Google test fails - #10512
Conversation
…est fails The Android Google test force-stopped Play services only when it reached the end. When a step failed first, Play services' add-account flow stayed in the app's task and later covered the home in the next test, which made token-cache-persistence/relaunch fail its first attempt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…kill Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 33aaf3b The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
No actionable comments were generated in the recent review.
|
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-biometrics
@clerk/expo-google-signin
@clerk/expo-native-components
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/mosaic
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Description
Follow-up to #10430. The Android Google sign-in test force-stops Google Play services so that Google's add-account flow can't cover the next test. That cleanup only ran when the test got to the end. If an earlier step failed, it was skipped.
That happened in run 40790794285 on the Version packages PR. The Google test's
google-system-promptscreenshot hit an agent-device snapshot error on Google's loading page, so the test stopped there. About 15 s into the next test,token-cache-persistence/relaunch, Google's "Sign in with ease" page came up over the app, and its third launch timed out waiting for the home. It passed on retry and was reported as flaky.google-sign-in-buttonfails, then rethrows the original error. If the force-stop itself fails, that error is dropped so the report keeps the real one.How it was tested, on a local Android emulator, with a temporary
throwadded right after thegoogle-system-promptscreenshot (not committed):adb shell dumpsys activity activitiesstill lists Play services' add-account activities in the app's task, includingMinuteMaidActivity(the "Sign in with ease" page from the CI failure). 15 Play services activity records in all.MinuteMaidActivityand the rest are gone. One finished, task-less record is left.token-cache-persistence/relaunchwith--retries 0: the relaunch test passed on its first attempt. On the old test, it also passed locally, so the local emulator doesn't reproduce the timing of the CI one. The activity check above is the direct evidence.integration/expo-nativetypecheck and unit tests pass.The Google test can still fail on its own when the screenshot lands on Google's loading page (this run, and 40362880088 before). This PR doesn't change that. It only stops that failure from spreading into the next test.
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
🤖 Generated with Claude Code