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-up.md

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

Sign up

A new user enters a test email or a test phone number, gives what the instance still requires, enters the code for each address, and lands signed in.

Sub-features

  • complete reaches the password step for a new test email, sets the run password, types 424242 on the code screen, and lands signed in.
  • complete-from-home does the same in the AuthView that the home's Sign in button opens, and that AuthView closes itself.
  • phone starts with a phone number, gives the email and the password that the standard settings require, verifies the email and then the phone with 424242, and lands signed in.

How to get to it (user POV)

  • Open AuthView in sign-up mode, type an email, tap Continue, type a password, tap Continue, then type the code.
  • For a phone sign-up, tap Use phone number on the start screen, type the number, and tap Continue. Type an email, tap Continue, type a password, tap Continue, then type the emailed code and the SMS code.

Driving it with verify

Preconditions:

  • Each test gets an email from host.newEmail() and launches with authMode: 'signUp', then taps e2e.auth.signInFullScreen. The second test of complete.e2e.ts taps e2e.auth.signIn instead. e2e-tests/bin/control-clerk-android down deletes the user the form creates.

  • The standard settings take a phone number at sign-up and verify it by SMS code, and they still require an email and a password. phone.e2e.ts gets a number that no user holds from host.newPhone().

  • Password step. Run e2e-tests/bin/control-clerk-android run sign-up/complete. It fills clerk.auth.start.identifier, taps clerk.auth.start.continue, and expects clerk.auth.signUp.password and clerk.auth.signUp.continue. Screenshot signup-password.

  • Request code. It then fills clerk.auth.signUp.password with runPassword(host.runId), taps clerk.auth.signUp.continue, and expects clerk.auth.signUp.code. Screenshot signup-code.

  • Complete. After the code screen it fills CLERK_TEST_CODE and waits for the home to show Signed in as the new email with a user ID. Screenshot signed-up.

  • Complete in the AuthView the home opens. The second test of complete.e2e.ts taps e2e.auth.signIn and does the same steps in the AuthView with a close button. The home closes that AuthView only in onAuthComplete, in onDismiss, or on back. The test neither closes it nor presses back, so Signed in as the new email on the home proves that onAuthComplete ran. Screenshot signed-up-from-home.

  • Sign up with a phone number. Run e2e-tests/bin/control-clerk-android run sign-up/phone. It taps clerk.auth.start.identifierSwitcher, fills clerk.auth.start.phoneNumber with the ten digits of the number, and taps clerk.auth.start.continue. It fills clerk.auth.signUp.emailAddress with the email and clerk.auth.signUp.password with the run password, and taps clerk.auth.signUp.continue after each. It expects Check your email with the email on the code screen, and fills clerk.auth.signUp.code with CLERK_TEST_CODE. Screenshot signup-phone-email-code. It expects Check your phone with the number as Clerk formats it, fills the code again, and waits for the home to show Signed in as the email with a user ID. Screenshots signup-phone-code and signed-up-with-phone.

  • Proof. Both specs pass. run.json lists the email under identities with the id of the user the form created.

States a spec cannot reach

State Where the app decides What it takes
The email link step auth/AuthRouting.kt, when signUp.isEmailLinkVerificationSupported is true The email link, which the standard instance turns off. A spec turns it on with host.useSettings({ config: { 'auth_email.verification_strategies': ['email_code', 'email_link'] } }), as references/instances.md lists. No committed spec does

Gotchas

  • Android asks for the password before the code.
  • A phone sign-up collects everything before it verifies anything: the email, then the password. It then verifies the email before the phone.
  • Both code screens use clerk.auth.signUp.code. Their titles tell them apart, Check your email and Check your phone, and neither title has a test tag, so those checks use text.
  • The steps that collect a field, such as the password, the code steps, and the complete-profile step, show Sign up in their top bar, above the step's own title, and that top bar title has no test tag. The email link step, which the standard instance does not reach, has no Sign up in its top bar. Tell the steps apart by their fields or their own titles, not by Sign up.
  • The phone code screen shows the number formatted, +1 201-555-01xx. asShownByClerk(phone) in specs/phone.ts gives that text.
  • The password field withholds its value from the screen tree. host.fill types the password once and cannot confirm that it landed, so assert on what the form does next.

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