Auth bypass deep links are useful when your tests are not specifically about authentication. Logging in or completing sign-in flows can take a long time, so bypassing authentication lets you jump straight to the part of the app you actually want to test.
The easiest implementation is:
- Add a test-only deep link handler in your app.
- Gate that handler with Revyl launch variables.
- Open one deep link from
revyl device navigate or a YAML navigate step.
Only enable this in simulator, staging, debug, or explicit test builds. Do not ship a permanent auth bypass in production.
Fastest Path For Expo Cloud Agents
Use this path when you already run an Expo development client through revyl dev.
Load the Expo dev client project first, then send the app-specific auth deep link. In managed Expo apps, JavaScript may not automatically see native launch values; use a small native config bridge, verify the token with a staging backend, or use a local demo fallback for sample apps only.
Copy This Contract
Use one route shape across every framework:
Create these launch variables:
Then start a device with the variables attached and open the bypass link:
Use the same URL in YAML tests:
