Assets

Assets are organization-scoped app artifacts used by run.cloud mobile sessions. They can be uploaded directly or created from a verified Xcode build output.

runcloud asset push ./MyApp.tar.gz -n my-app --org-id "$RUN_CLOUD_ORG_ID"
runcloud asset list --org-id "$RUN_CLOUD_ORG_ID"
runcloud asset pull <asset-id> -o ./MyApp.tar.gz
runcloud asset delete <asset-id>

Use assets when CI or an agent needs to install the same build into multiple simulator sessions. Build output Assets are immutable. Their metadata includes the originating build, native fingerprint when available, and parentAssetId for a JavaScript rebundle. They follow the build’s retention policy and reject asset delete. Use one retry-safe operation to install an existing Asset on a new host:

runcloud mobile launch \
  --asset <asset-id> \
  --idempotency-key "launch-<your-stable-intent>" \
  --platform ios \
  --json

The Asset remains an authenticated identity. The API creates a short-lived read URL only after checking that the Asset and target session have the same organization; no build or simulator host receives another host’s credentials. Accepted artifact extensions are intentionally broad, but iOS Simulator installation works best with zipped simulator .app bundles or simulator archives produced by your build system.

Getting Started

Linux Sandboxes

CI

Integrations

Platform

iOS

Android

Billing

Agents