Name: Native Update
Author: Native Update

Question 1

Can a live update change native code?

Accepted Answer

No. Live updates carry web-layer changes: HTML, CSS, JavaScript and web assets. Native code, a new Capacitor plugin or a new permission ships as a store build, and Native Update can then prompt users to install it.

Question 2

What happens if a new bundle crashes on launch?

Accepted Answer

If the bundle never calls notifyAppReady(), the native layer reverts it after two cold starts and the app opens on the last good bundle. The dashboard counts it as a failed start.

Question 3

How do I roll back a release?

Accepted Answer

Roll it back in the dashboard or with the CLI. Devices return to the previous good bundle on their next check, and the release stays in your list for later.

Question 4

Is iOS supported?

Accepted Answer

The plugin includes iOS code, but it has not had on-device sign-off yet. Android is the platform releases are tested on today.

Question 5

What counts as a monthly active user?

Accepted Answer

A unique device that checks for an update at least once in a rolling 30-day window. A device that stops checking in drops off the count after 30 days.

Question 6

What happens when I go over my plan’s limit?

Accepted Answer

Uploads and promotions pause, and the dashboard and an email tell you. Devices keep the release they have. Seven days after a plan expires, update delivery stops until billing is fixed.

Question 7

Do I need a Native Update account?

Accepted Answer

Yes. The plugin talks to the Native Update service with your app’s API key. The Free plan includes every feature, up to 30 apps and 5,000 monthly active users.