---
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


---

# Test and publish an updated iOS app for public distribution

# Test and publish an updated iOS app for public distribution {#ariaid-title1}

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

After you have requested an updated iOS branded mobile app for public distribution, perform these steps to test and publish it.

## Before you begin

Role required: admin

## Procedure

1. When the build status of your app becomes Ready for testing, you can download the XCArchive file, edit it and sign it, and then use XCode to upload it to App Store Connect.  
   Note:  
   * After you upload the XCArchive file and the new build is published to your TestFlight testers group, then your testers receive an email with a link to test your branded app.
   * You don't need to create a new Apple iOS Distribution Certificate or a provisioning profile for apps that already exist and you're only updating the version number. For example, updating version 17.5 to 18.0. However, if your certificate has expired per your Keychain Access program on your Mac, see [KB0997467](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0997467) for instructions.
   {#testpub-updat-ios-app-pub__ul_smd_h5j_l2c}
2. When your testers receive an email from Apple TestFlight with a link to test your branded app, use TestFlight to check the following if they've changed from your original request:  
   * App has the correct name, icon, splash screen, branding, and theming. For more information, see [Create a theme with Theme Builder](https://www.servicenow.com/docs/access?context=tb-create-theme&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).
   * App uses the default instance you specified for login if you selected the instance pre-fill option when you requested the branded app.
   * EULA and privacy policy listed in the mobile app Settings tab under Legal link to the policies you specified.

   {#testpub-updat-ios-app-pub__ul_lpc_kxc_j2c}

   See [Apple documentation](https://developer.apple.com/testflight/) for information about using TestFlight.
3. Set up your branded iOS app for public distribution:  
   * Set up push notifications by downloading the Apple push certificate (`p12` file) and uploading it to your app's push application record:
     * Create your push notification certificate (`p12` file). For instructions, see [KB1506609](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1506609).
     * Access the Push Applications table on your instance by navigating to AllPush Application.
     * Configure your push applications. For instructions, see [Configure push applications for iOS branded apps using certificate based authentication](https://servicenow-prod.fluidtopics.net/Pwaez8w_JgpwjR_gzfqzxQ "Install an iOS push certificate to use push notifications on your branded ServiceNow mobile apps for iOS.").
     * (Optional) Test your push notifications by using out-of-the-box configurations. For more information, see [KB0829093](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0829093).
     {#testpub-updat-ios-app-pub__ul_wjw_nyc_j2c}
   * If you updated your universal links table with new instance URLs, you must upload the new universal links file to each of those instances:  
     Download the universal links file (AASA) in the Your app's info tab under the App info section and follow the instructions in the following KBs:
     * See [KB1273622](https://support.servicenow.com/kb?id=kb_article_view&sys_kb_id=3c08eadcdb556154fd8d2b69139619b3) for more information about deep links and universal links.
     * See [KB0831613](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0831613) for information about how to upload your universal link AASA file.
     {#testpub-updat-ios-app-pub__ul_aph_3zc_j2c}
   {#testpub-updat-ios-app-pub__ul_rnd_fyc_j2c}
4. Once your TestFlight testers have tested your app for branding requirements and functionality:  
   * Reject the app to edit the branding, app name, app type, or any third-party information. Use the Duplicate option to copy information over to a new app request after have rejected the app. See the FAQ on the home page of the Mobile Publishing app for information about what you can change without having to create a new branded app request.
   * Approve the build to move forward with publishing the app to your end users.
   {#testpub-updat-ios-app-pub__ul_vxc_vzc_j2c}
5. **Optional:** Customize your app's workflows:  
   Use Mobile App Builder to customize your app. See [Mobile App Builder](https://servicenow-prod.fluidtopics.net/D7JsRshhaXqbaFuveRefbA "The ServiceNow Mobile App Builder (MAB) is a configuration tool to build and manage screens and records that make up workflows within ServiceNow mobile apps. The organizational layout and navigation options in the Mobile App Builder facilitate a faster and more intuitive creation of ServiceNow mobile applications.") for detailed information about how you can customize your branded app.
6. Publish your updated iOS branded app for public distribution.  
   Your app store listing definition remains the same as your previous version of this app. Update the "What's new" field in the app store listing and submit for Apple's approval. Apple conducts a final review before posting the app to the public App Store. If you have problems, file a ServiceNow Support case.
   * See [KB1649415](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1649415) for ServiceNow's Apple App Store listing guidance.
   * See [Apple documentation](https://developer.apple.com/ios/submit/) that explains how to list a public app on the Apple App Store.
   * For information about ServiceNow mobile apps version history and changes, see:
     * Now Mobile
     * ServiceNow Agent
     * Custom app
     {#testpub-updat-ios-app-pub__ul_pgk_lbd_j2c}
   {#testpub-updat-ios-app-pub__ul_nhq_z1d_j2c}
7. Update your app before you update your ServiceNow family version, or at least once per year to keep your push notifications working and to leverage the most up to date ServiceNow mobile features.  
   For more information, see [Tested devices and supported versions for ServiceNow mobile apps](https://servicenow-prod.fluidtopics.net/KbgnLcYnaX_y4UQuL6sEyA "Use the following information to verify that your mobile devices and operating systems are ready to use ServiceNow mobile apps.").

*[\>]: and then