Sign in with a passkey or an email code
Every plan
Passwords get reused, forgotten and typed into the wrong page. Your AppForShare account holds store keys, builds and client work, so signing in should be both easy and hard to steal.
Add a passkey and sign in with your fingerprint, face or device PIN, with no email or password typed. Or ask for a one time code by email. Your password, Google and GitHub sign in and two step sign in keep working.
Example
Settings, Passkeys
- MacBookSynced, last used today
- Pixel 8Added Nov 9, 2026
- Two step sign inOn, a passkey can replace the code
Made for
- Anyone who signs in on several computers and phones
- Teams that want stronger sign in without hardware to hand out
- People who signed up with email and forget the password
What it ends
- Password resets every few weeks
- Typing a password and an authenticator code on every new device
- Shared or reused passwords on a work account
How it works
Step 1
Add a passkey
In Settings, Passkeys, add one and confirm with your fingerprint, face or device PIN. Add up to 10, rename them, and remove any you no longer use.
Step 2
Sign in with it
On the sign in page, choose "Sign in with a passkey". It opens a session at once, with no email or password typed.
Step 3
Or ask for a code
"Email me a sign in code" sends 6 digits that work once, for 10 minutes.
Passkeys
A passkey is a key pair made by your device or password manager. AppForShare stores only the public key, a counter, transports, the name you give it and dates; the private part stays with your device or password manager. User verification is required, so a passkey works only after your fingerprint, face or device PIN.
With two step sign in turned on, a passkey of the same account can be used instead of the authenticator code. You get an email whenever a passkey is added or removed.
One time email code
The code has 6 digits, works once and lasts 10 minutes, with 5 tries and at most 3 codes per address in 15 minutes. The page gives the same answer whether or not the address has an account. Signing in with a code marks your email as verified. If two step sign in is on, it still asks for its code after the email code, as after a password reset.
Good to know
- Passwords stay: this adds ways to sign in, it does not remove one.
- On the web. The AppForShare app keeps password, Google, GitHub and the authenticator code; the CLI signs in with a token.
- No SMS codes and no Sign in with Apple.
Questions
- Which plan do I need?
- None. Passkeys and email codes work on every plan with an account.
- Do passkeys work with my password manager?
- Passkeys work with your device or a password manager that stores passkeys.
- What if I lose my phone?
- Sign in with a passkey on another device, your password, Google or GitHub, or an email code, then remove the lost passkey. Recovery codes still work for two step sign in.
- Does the email code skip two step sign in?
- No. If two step sign in is on, it asks for its code after the email code.
Read next
Try it on your own app
Free account in a minute. Pro starts with a 7 day free trial.
More features
- Builds on GitHub Actions
- Flutter builds on GitHub Actions
- Flutter facts and checks
- Security scan on every build
- Connect Expo (EAS builds)
- Connect Codemagic
- Send store builds to TestFlight and Google Play
- TestFlight groups and beta review on send
- TestFlight feedback in your inbox
- iOS device registration
- Hands free device setup
- Store listing editor
- App Store submission
- Google Play releases
- TestFlight tester sync
- Tester app with notifications
- Tester groups and status
- Join links for testers
- Beta and Live channels
- Build history page
- Tasks and activity feed
- Feedback to Linear and Jira
- Release checklist, approvals and blockers
- Release page per version
- Install link controls
- Several links per build
- Retire a test build
- TestFlight and APK in one link
- Install page in 13 languages
- In-app update check
- .aab uploads
- MCP server for AI tools
- Tester feedback with screenshots
- In-app feedback link
- AI test plan for each build
- Diawi compatible upload API
- Remember my iPhone
- Install help and why it failed
- Email the install link
- Custom channel address
- Verified publisher
- Daily install email
- Zipped .app upload
- Manage link for guest uploads
- Test accounts on the install page
- Telegram notifications
- Permissions in plain words
- Reply to testers and star ratings
- Follow a channel by email
- Download button for a README
- Store pages
- Check a build before upload
- Token scopes and CLI tools
- Upload from Claude or ChatGPT
- Free build tools
- How reports work
- Malware check on every upload