Index of every page on this site: llms.txt
All skills
clerk avatar

/verify-clerk-android

@4ee2671
by clerkclerk/clerk-android18 stars
17
Run it yourself

Drive the clerk-android SDK UI (AuthView, UserButton, UserProfileView, OrganizationSwitcher, OrganizationProfileView, session tasks) in the :e2e host app on an Android emulator, on this machine or on a CI runner, against a real Clerk development instance that the CLI creates and deletes, and capture video, screenshots, and the app log as evidence. Use it to prove any change to source/api, source/ui, or the :e2e host works before calling it done, to reproduce a UI bug, or to run the e2e tests.

  • 17 files
  • 155.5 KB
  • Updated 3 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/clerk/clerk-android/verify-clerk-android

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

featuressign-in-email-code.md

≈471 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Sign in with an email code

An existing user enters their email, gets a one-time code, and signs in with the code.

Sub-features

  • complete reaches the email code screen for an existing test user straight from Continue, stays on it, types 424242, and lands signed in.

How to get to it (user POV)

  • Open sign-in, type the email, tap Continue. On the standard instance a user with no password lands on the email code screen ("Check your email"). Type the code.

Driving it with verify

Preconditions:

  • The spec seeds a +clerk_test user on the standard instance and launches with authMode: 'signIn', then taps e2e.auth.signInFullScreen.

  • Request code. Run e2e-tests/bin/control-clerk-android run sign-in-email-code/complete. It fills clerk.auth.start.identifier, taps clerk.auth.start.continue, expects clerk.auth.signIn.code, and expects it still on screen 3 seconds later, with the email on the code screen. Screenshot code-screen.

  • Complete. After the code screen it fills CLERK_TEST_CODE and waits for the home to show Signed in as the seeded user's email with that user's ID. Screenshot signed-in.

  • Proof. The spec passes, and screenshot signed-in shows the home with the seeded user's email and ID.

Gotchas

  • The spec checks the code field a second time after 3 seconds. A sign-in that shows the code screen for a moment and then leaves it would pass a single visibility check.
  • The standard instance has the email link off, because a test address gets no mail, so a run has no link to follow. With the link on, AuthView opens the email-link screen first. It has the same title as the code screen, "Check your email", and no code field, so clerk.auth.signIn.code tells them apart. A spec that needs the link sets auth_email.sign_in_strategies and auth_email.verification_strategies with host.useSettings.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 4ee2671. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago

README badge

README badge for clerk/clerk-android/verify-clerk-android