Documentation
Everything to ship over-the-air updates with Pulsar — from install to multi-deployment testing.
Release safety
Each app has a health gate: a rollback rate and a minimum number of devices. When a release crosses it, admins are emailed and, if the release is on a gradual rollout, the rollout stops adding devices. Resume it from the release, or roll back. Change the gate under the app’s Release health gate panel.
Turn on Requires approval for a deployment and every new release waits until a second admin or owner approves it. Devices keep the current release until then. The CLI prints when a release is waiting.
With SDK 1.7.0 or later, a rollback reports the JavaScript error that caused it. The CLI uploads the bundle’s source map with each release, so stacks in the failed-installs view point at your own files. Pass --no-sourcemap to skip the upload.
A Hermes bytecode release uploads one map for the bytecode and one for its JavaScript copy, so on apps without private bundles stacks map to your files whichever one a device runs.
The CLI warns when a bundle is more than 20% larger than the previous release and when no device has reported the store build you’re targeting. --max-growth 30 refuses to release anything that grew more than 30%.
For bytecode releases both checks compare like with like: bytecode with the last bytecode release, and the JavaScript copy with the last JavaScript. The first bytecode release doesn’t trip them.