---
sourceDocument: Australia Mobile Configuration and Navigation
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Mobile Configuration and Navigation

ft:clusterId :

    - mobile

bundleId :

    - mobile

workflow :

    - Development, Data and Analytics


---

# Build statuses

# Mobile Publishing build statuses {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Learn what the Mobile Publishing build statuses "Build in progress" and "Ready for testing" mean and what actions they require from you.

## "Build in progress" {#mob-pub-build-statuses__section_rdj_rxn_k2c}

Your app's build status is "Build in progress" while ServiceNow® creates your branded app and sends it to Apple or Google for approval. The time to build is based on whether your app uses public or private distribution and on which operating system you choose. The time to build process takes the amount of time shown in the following
diagram:

## "Ready for testing" {#mob-pub-build-statuses__section_hbs_czn_k2c}

When the build status becomes "Ready for testing," one of the following actions is required based on the following factors:

* Operating system
* Whether the branded mobile app is for private or public distribution
* Type of mobile application management (MAM) you use
* If the request is for a new branded app or a request to update an existing branded app
{#mob-pub-build-statuses__ul_gcc_fzn_k2c}  
{#mob-pub-build-statuses__table_fsc_rzn_k2c__entry__4}

| New/Update | Operating System | Private/Public distribution | "Ready for testing" action required |
|-|-|-|-|
| New | Android | Private | See [Test and publish a new branded Android app for private distribution](https://servicenow-prod.fluidtopics.net/EbjiBvMewAemBLCxJtvcmQ "Learn the next steps to test and publish a new branded Android app for private distribution after you request it in Mobile Publishing."). |
| New | iOS | Private | See [Test and publish a new branded iOS app for private distribution](https://servicenow-prod.fluidtopics.net/9qWTbtQC2J1XcT6Jw~83CA "Learn the next steps to test and publish a new branded iOS app for private distribution after you request it in Mobile Publishing."). |
| New | Android | Public | See [Test and publish a new branded Android app for public distribution](https://servicenow-prod.fluidtopics.net/FJjBCUZX_DKjPrsINV0BeA "Learn the next steps to test and publish a new branded Android app for public distribution after you request it in Mobile Publishing."). |
| New | iOS | Public | See [Test and publish a new branded iOS app for public distribution](https://servicenow-prod.fluidtopics.net/JKpwpF71RVBGRx8vNZxKwQ "Learn the next steps to test and publish a new branded iOS app for public distribution after you request it in Mobile Publishing."). |
| Updated | Android | Private | See [Test and publish an updated Android app for private distribution](https://servicenow-prod.fluidtopics.net/IeKpC1_S~lcJHXzF~peAWA "After you have requested an updated Android branded mobile app for private distribution, perform these steps to test and publish it."). |
| Updated | iOS | Private | See [Test and publish an updated iOS app for private distribution](https://servicenow-prod.fluidtopics.net/tg6Cb1X36ig1KEfD6Upveg "AFter you have requested an updated iOS app for private distribution, perform these steps to test and publish it."). |
| Updated | Android | Public | See [Test and publish an updated Android app for public distribution](https://servicenow-prod.fluidtopics.net/RSsakXA41OT03bB6DfXmxw "After you have requested an updated Android app for public distribution, perform these steps to test and publish it."). |
| Updated | iOS | Public | See [Test and publish an updated iOS app for public distribution](https://servicenow-prod.fluidtopics.net/GzyWfjgkCM~rrZZk2TAh5Q "After you have requested an updated iOS branded mobile app for public distribution, perform these steps to test and publish it."). |
[Table 1. "Ready for testing" actions required]

{#mob-pub-build-statuses__table_fsc_rzn_k2c}

