Third-Party Services
Only needed if you're self-hosting. The Quick Start runs against our deployed sandbox using demo credentials that are already filled in .env.example. Follow the pages below only when wiring the app to your own auth-svc — and remember the app's Auth0 and FaceTec values must match your auth-svc configuration.
The boilerplate integrates four external services. All four are required when self-hosting.
| Service | Used for | .env keys |
|---|---|---|
| Auth0 | Email / social login → JWT for API auth | EXPO_PUBLIC_AUTH0_DOMAIN, EXPO_PUBLIC_AUTH0_CLIENT_ID, EXPO_PUBLIC_AUTH0_AUDIENCE |
| Google Sign-In + Drive | Social login + backup encryption key storage | EXPO_PUBLIC_WEB_CLIENT_ID, EXPO_PUBLIC_IOS_CLIENT_ID, EXPO_PUBLIC_IOS_URL_SCHEME |
| WalletConnect (Reown) | Connect to dApps via QR code | EXPO_PUBLIC_WALLET_CONNECT_PROJECT_ID |
| FaceTec | 3D biometric scan for backup and recovery | EXPO_PUBLIC_FACETEC_DEVICE_KEY_IDENTIFIER, EXPO_PUBLIC_FACETEC_URL, EXPO_PUBLIC_ENCRYPTION_KEY |
Self-hosting checklist
Complete this checklist in order. Auth0 blocks login, so it must come first.
- Create the Auth0 React Native app, API, callback URLs, and optional login methods. Add
EXPO_PUBLIC_AUTH0_DOMAIN,EXPO_PUBLIC_AUTH0_CLIENT_ID, andEXPO_PUBLIC_AUTH0_AUDIENCEto the app. The domain and audience must matchAUTH0_DOMAINandAUTH0_AUDIENCEinauth-svc. - Create Google OAuth clients and enable Drive. Add
EXPO_PUBLIC_WEB_CLIENT_ID,EXPO_PUBLIC_IOS_CLIENT_ID, andEXPO_PUBLIC_IOS_URL_SCHEMEto the app. - Create a Reown WalletConnect project. Add
EXPO_PUBLIC_WALLET_CONNECT_PROJECT_IDto the app. - Add FaceTec development or production credentials. Add
EXPO_PUBLIC_FACETEC_URL,EXPO_PUBLIC_FACETEC_DEVICE_KEY_IDENTIFIER, andEXPO_PUBLIC_ENCRYPTION_KEYto the app. The FaceTec device key must match the FaceTec key configured inauth-svc.