Add Phone Authentication to Your React Native App
Use the Glide React Native SDK with your existing backend proxy. The SDK selects the carrier strategy (TS43 or Link) from the prepare response — branch your code on the strategy, not on Platform.OS.
Install the SDK
Install from npm (same package as the public registry).
For air-gapped CI, contact your Glide integration lead for a vendor-hosted tarball, or mirror locally with npm pack @glideidentity/glide-fe-sdk-react-native.
Android: set compileSdkVersion = 35 in android/build.gradle for the Digital Credentials API.
Configure PhoneAuthClient
Point endpoints at routes on your backend. The SDK never calls Glide directly.
Prepare → Native prompt → Verify
Use the three-step flow so you control UI between session start and completion.
If prepared.authentication_strategy === 'link', the carrier returns through a Universal Link / App Link — register a Linking listener and forward those URLs to glide.handleDeepLink(url). The same code works on iOS and Android. usePhoneAuth() does this for you.
Forward deep links (Link strategy)
Skip this step if you're using usePhoneAuth() — the hook registers the listener for you on both iOS and Android.
If you're using PhoneAuthClient directly, register a Linking listener and gate it with isGlideDeepLink(url) so the SDK only sees URLs that are actually a carrier callback. Other deep links your app receives keep flowing to your own router.
Backend proxy routes
Expose prepare, process, and optionally report-invocation using the Glide backend SDK (Node.js, Go, or Java).
See the Node.js quickstart for a full Express example.
Next steps
- Package README on npm — iOS Universal Links (AASA), Android setup
- Magical Auth overview
- Error handling
npm install @glideidentity/glide-fe-sdk-react-native