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.

featuressession-persistence.md

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

Session persistence

A signed-in user closes the app and opens it again. The app starts signed in, with the same session, and asks for nothing.

Sub-features

  • relaunch restores the session from the app's storage after the app process is stopped and started again.

How to get to it (user POV)

  • Sign in, close the app, and open it again.

Driving it with verify

Preconditions:

  • The spec seeds a +clerk_test user and signs in with a ticket on the home. It runs on the standard settings.

  • Relaunch. Run e2e-tests/bin/control-clerk-android run session-persistence. The spec reads the session ID on the home (e2e.auth.sessionId), then launches again with keepStorage: true and no signedInAs. That launch stops the process and starts it with the same storage scope and no sign-in ticket. The spec waits for the home to show the same user, and expects the same session ID. Screenshot relaunched.

  • Proof. specs/features/session-persistence/relaunch.e2e.ts passes. The video shows the home with the user, the app closing, and the home with the same user and session ID.

Gotchas

  • Only the second launch tests persistence. It carries no ticket, so the only way the home can show a user is the session that the SDK stored on the device.
  • A launch with keepStorage and no signedInAs needs landsOn, because the fixture cannot know what stored state should show. The spec names host.app.signedIn.
  • The SDK keeps its state in the shared preferences file clerk_preferences. The host deletes that file when a launch names a storage scope other than the one of the launch before it, which is how every other launch starts signed out. A launch with keepStorage: true names the same scope, so the file stays.

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