What Update Policies Are

Update policies control when an available OTA bundle should be downloaded and applied after your app checks for updates.

They are most commonly used with BundleDrop.init, which owns the startup flow for you.

Available Policies

Bundle Drop supports three policies:

• manual
• on-next-launch
• immediate

manual

manual means Bundle Drop does not automatically download or apply updates.

This is the best fit when you want a user-driven update flow, such as a settings screen or an update prompt with explicit buttons.

Teams usually pair this with useBundleDrop.

on-next-launch

on-next-launch means Bundle Drop downloads the update when it is available, stages it, and waits until the next app launch to apply it.

This is a good default when you want an automated flow without reloading the app immediately in the middle of a session.

immediate

immediate means Bundle Drop downloads the update and applies it as soon as possible.

This is useful when you want updates to take effect right away, but it is also the most aggressive option because it can interrupt the current session.

How This Fits with BundleDrop.init

BundleDrop.init is the main place where update policies matter.

It runs the automated startup flow and uses the selected policy to decide what should happen when a new update is available:

• manual: initialize runtime state, but do not automatically download or apply
• on-next-launch: download now, apply on the next app launch
• immediate: download now, apply right away

Choosing the Right Policy

A practical way to choose:

• use manual for user-controlled update UX
• use on-next-launch for most production apps
• use immediate when you want the fastest possible update adoption

Related Docs

• For the startup controller, see BundleDrop.init.
• For manual update flows, see useBundleDrop.
• For reverting a bad release, see Rollback.