Deploy a Live Update
The Ionic Deploy feature works by using the installed Appflow SDK in your native application to listen to a particular Deploy
When a Deploy build is assigned to a Channel, that update will be deployed to user devices running binaries that are configured to listen to the specified Channel.
Nomenclature note: The terms "Deploy build", "web build", "live deploy" and "live update" can be used interchangeably. They all refer to an update provided to your user's device by Appflow's Deploy feature.
In order to deploy a live update, you will first need to create a
There are two ways to do this:
- Click the
Start web buildicon from the
- Click the
New web buildbutton in the top right from the
Deploy > Buildstab
You will need to make sure you've selected the correct commit to deploy. If your plan includes
Once the build begins you will be able to watch it's progress and look at the logs if you encounter errors.
Note: If you have trouble getting a successful build in the previous step, you can find answers to common Deploy build errors in this section of our knowledge base.
Once you have a successful Deploy build, you can assign it to the same Channel you configured the Appflow SDK to
listen to when you installed it by clicking the
Assign to channel button in the top right of the build detail
page. You can also click the
Assign to channel icon on the build in the
Deploy > Builds tab and select the Channel
from the dropdown.
For your application to receive a live update from Deploy, you'll need to run the app on a device or an emulator. The easiest
way to do this is simply to use the
If the app is configured correctly to
listen to the channel you deployed it to, the application should update immediately on startup if you're using the
If you're using the
Generally speaking, if you are developing using an emulator and live reload you probably do not want Deploy to be active, as it can intefere with your local development.
We recommend setting the
true in the
config.xml file during local development. You can then set it back to
false before building your binary for release by either manually setting it
back or using the