Revyl Documentation

Frameworks

Frameworks

Pick your framework for build and session setup, and see which frameworks hot reload.

Pick your framework to see how to build it and open it in a Revyl session.

Web

Mobile

Mobile apps use the Revyl dev loop.

Hot Reload vs Rebuild

Web

FrameworkDev Loop ModelWhen to Rebuild
Next.jsBuild a standalone server bundleRebuild and open the new build after a code change
Static ViteBuild a static bundleRebuild and open the new build after a code change
Any deployed Web frameworkRegister the hosted HTTPS previewDeploy the change, register the preview URL, and open that build

Web does not use a Revyl hot-reload provider.

Mobile

FrameworkDev Loop ModelWhen to Rebuild
Swift/iOSRebuild on every changeEvery code change (binary is the app)
Android NativeRebuild on every changeEvery code change (binary is the app)
React Native (bare)Hot reload (JS/TS changes are live)Only when native dependencies change
ExpoHot reload (JS/TS changes are live)Only when native dependencies change
FlutterRebuild on every changeEvery code change (Dart compiles into the binary)

For Expo and React Native, the uploaded build is a "dev client shell" -- your JS/TS code is served live from your local Metro server via a Revyl relay. For Flutter, Swift, and Android, the binary is the app.

Platform Build Requirements

Web

PlatformRequirements
Web bundleOne dedicated output directory. Static output needs a root index.html; server output needs its runtime dependencies and an explicit run.start. See Web builds.
Web deployment URLAn existing HTTPS preview, with no URL credentials, query string, or fragment. See deployed previews.

Mobile

PlatformRequirements
iOS and AndroidA simulator .app or an emulator-compatible .apk. See Build Artifact Requirements.

The mobile frameworks' default debug builds satisfy their artifact requirements. For custom configurations — narrowed abiFilters, release builds, or .ipa archives — check the full rules and trade-offs.

Hot reload and rebuild configuration

Web

Web recipes are authored explicitly; revyl init does not detect Next.js, Vite, package managers, or preview hosts.

FrameworkHot ReloadRebuild Dev LoopProvider Name
Next.jsNot supportedrevyl build --profile preview --platform web, then start a new session—
ViteNot supportedrevyl build --profile preview --platform web, then start a new session—
Deployed Web previewNot managed by RevylRegister the updated preview URL, then start a new session—

Mobile

revyl init best-guesses mobile build and dev-loop configuration.

FrameworkHot ReloadRebuild Dev LoopProvider Name
Swift/iOS—[r] rebuild + reinstallswift
Android Native—[r] rebuild + reinstallandroid
React Native (bare)Fully supported[r] for native changesreact-native
ExpoFully supported[r] for native changesexpo
Flutter—[r] rebuild + reinstall—
Kotlin Multiplatform—[r] rebuild + reinstall—
Bazel—[r] rebuild + reinstall—

Bazel and Kotlin Multiplatform are detected as build-tool or layout signals, not as supported build.framework values. A project with both native apps uses framework: ios and builds each recipe for its own platform.

Dev Loop Framework Troubleshooting

Web

SymptomCauseFix
Web: no recipe after revyl initWeb setup is manualCreate a Web app and add the Next.js or Vite recipe, or register a preview
Web: profile <name> is URL-onlyThe profile has an app ID but no managed build recipeRegister the preview URL, or add explicit build_commands and output_path
Web: server health check failsThe server is bound to localhost or the health check does not return 2xx or 3xxBind to 0.0.0.0; match run.port and run.healthcheck to the app
Web: static bundle rejectedNo root index.html in the output directoryPoint output_path at the built static site, not the source directory

Mobile

SymptomCauseFix
"Detected Swift/iOS instead of Expo"Detection ran outside the Expo app root or expo is absent from its local package.jsonRun revyl init --detect from the app directory; if needed, edit build.framework and the generated profile, then validate
"Detected Android instead of Expo"Detection ran outside the Expo app root or the native directory won an ambiguous matchRun revyl init --detect from the app directory; if needed, edit build.framework and the generated profile, then validate
"No providers detected"Missing package.json, wrong directory, or no framework indicatorscd to the app directory; verify package.json has expo or react-native
"App scheme empty"The Expo app config does not resolve a custom schemeConfigure expo.scheme in the app, rebuild the dev client, and use the new build
"No runnable development recipe"The project config has no usable profile/platform recipeEdit the generated named profile and run revyl config validate
"Port 8081 is already in use"Another Metro instance runninglsof -ti:8081 | xargs kill or --port 8082
"No application is registered to handle this URL scheme"The installed dev client does not register the scheme recorded with the buildCorrect the Expo app's scheme/generated-scheme settings, rebuild, and use the new build
No URL scheme in the appApp only uses universal linksAdd "scheme": "myapp-dev" to app.json, rebuild dev client
No eligible iOS or Android recipeThe selected named profile lacks that platform recipeEdit the profile in .revyl/config.yaml, then run revyl config validate
Deep link fails with LSApplicationWorkspaceErrorDomain error 115The URL scheme in the deep link doesn't match any installed appSame as "No application is registered" above
App closes briefly after tapping "Open" in the dialogNormal: dev client is reloading to connect to Metro via tunnelWait for it to reopen; if it doesn't, check Metro output for JS errors
"Open in [App Name]?" confirmation dialogiOS system prompt for URL scheme handoffsTap "Open" to proceed; this is expected behavior

On this page