Skip to main content

​
Build Guidance

To use the Dev Loop, a build is required on every code change. The binary is the app — see Dev Loop: Hot reload and rebuild configuration for the full breakdown. To capture sanitizer findings, upload a simulator build compiled with the corresponding sanitizer enabled. See iOS runtime diagnostics for supported diagnostics and how to view findings.

​
Build via the Revyl CLI

​
Prerequisites

  • Revyl CLI installed and authenticated (revyl auth login)

​
Setup

Initialize the project using the Revyl CLI:
This detects the Xcode build and writes a named profile with its iOS recipe. Review or fill in the app ID, commands, and output path before the first build.

​
Run Build

Run a build using: revyl build --profile development --platform ios This runs the selected recipe in the cloud. If your profile has a different name, pass it explicitly; no profile is active/default. See Configuration.

​
Advanced Configuration

Revyl makes a best effort to determine the build commands to be used. If the build does not complete successfully modify the build commands manually in the config.yaml file.

​
Build via XCode UI

​
Select Simulator

In Xcode toolbar:
  • Choose your app scheme
  • Select any iOS Simulator (e.g., iPhone 15 Pro)
The specific simulator doesn’t matter - builds are universal.

​
Build

  1. Clean: Product → Clean Build Folder (⌘+Shift+K)
  2. Build: Product → Build (⌘+B)
  3. Wait for success

​
Locate Build

Product → Show Build Folder in Finder Navigate to:
Important: Use Debug-iphonesimulator, NOT Debug-iphoneos.

​
Test Before Upload

  1. Open iOS Simulator
  2. Drag YourApp.app onto simulator window
  3. Launch from home screen
  4. Verify it works
Always test locally before uploading.

​
Upload to Revyl

See Ways to Add Builds to upload the build to Revyl.

​
Auto-Detect Build from DerivedData

If you build in Xcode normally (Cmd+B), revyl dev automatically finds the most recent simulator .app from DerivedData:
The CLI scans ~/Library/Developer/Xcode/DerivedData/ for the most recently modified .app matching your project. Test runner bundles (*Tests.app) are excluded automatically.

​
Troubleshooting

Simulator builds don’t require an Apple distribution certificate or provisioning profile. Let Xcode apply its default local signature so the app retains entitlements used by services such as Keychain. Don’t set Code Signing Identity to “Don’t Code Sign” or pass CODE_SIGNING_ALLOWED=NO.
Revyl’s simulators run arm64, so your simulator build must include an arm64 slice:
  1. Select your target → Build Settings
  2. Find Architectures and verify Standard Architectures - $(ARCHS_STANDARD)
  3. Find Excluded Architectures and make sure arm64 is not excluded for Any iOS Simulator SDK, in your target or in your Pods project
Check the result with lipo -archs YourApp.app/YourApp; the output must include arm64.
  • Drag the .app file directly (not a folder)
  • Restart iOS Simulator
  • Check simulator iOS version matches deployment target
Manual path: