Phased Releases
Updated: Dec 19, 2024
Phased Release allows you to release builds to users gradually over time rather than 100% at once. This allows for a more controlled release where regressions can be discovered early on.
The release cadence is currently set to 5% → 20% → 50% → 100%, with 48 hours in-between every phase. However, you may advance to the next phase at any time.
On the left nav go to Distribution > Release Channels and click into Production (Store)
Under the Channel settings tab, set the Release Method to Phased release
Starting a Phased Release
A Phased Release will be tied to your build when it goes live.
Note that a Phased Release will not happen for your first ever build release (initial submission), only subsequent build updates after that.
Your build will go live by pushing your build to the Production (Store) release channel in Approved state via
- Meta Quest Developer Hub (MQDH)
- CLI
- Developer Dashboard
- Scheduled App Submission Release
- Pushing from another release channel
- Change Current Build
Monitoring a Phased Release
You can view your Release Status and % progress in the Current Builds tab of the Production (Store) release channel
Select the Phased releases tab to see more details about your Phased Release progress
Your phased release will automatically advance to the next phase until it eventually hits 100%. However you can accelerate the release by utilizing the Jump to dropdown to immediately go forward into a future phase. Note that you cannot decrease your phase.
Clicking Pause Release will halt the countdown to the next phase. During this time, users who are eligible will continue to receive the new build.
Cancel Release will immediately set the roll out percentage to 0% and cancel the Phased Release. Your users will roll back to your previous build.
Pushing a new build during an ongoing Phased Release
If a Phased Release is ongoing and a new build with a higher version code is pushed to the Production (Store) channel, the new build will be added to the existing Phased Release for the same group of people. That is, if your phased release was at 50% and you uploaded a new build, the same 50% of people who saw the previous build would see the new one. This allows you to test fixes with the same group of people.
If you roll back to an older build (lower version code), your Phased Release will automatically be canceled.