Test and publish a new branded iOS app for public distribution

  • Release version: Zurich
  • Updated July 31, 2025
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Test and publish a new branded iOS app for public distribution

    This guide outlines the essential steps ServiceNow customers need to follow to test, set up, approve, customize, publish, and maintain a new branded iOS app for public distribution after requesting it through Mobile Publishing. It ensures customers can confidently deliver a fully branded, functional app via the Apple App Store.

    Show full answer Show less

    1. Test the app

    • After a successful build, download the iOS testing file from the Request details page in Mobile Publishing.
    • (Optional) If using Microsoft Intune MAM, register the app with Microsoft Entra ID before testing.
    • Provision the app by creating an app ID, distribution certificate, editing and signing the XCArchive file, and uploading it to App Store Connect using XCode.
    • Add testers to a TestFlight group on App Store Connect and publish the build to that group so testers receive invitations.
    • Use TestFlight to validate branding elements (name, icon, splash, theming), instance pre-fill for login, and legal documents like EULA and privacy policy.

    2. Set up the app

    • Configure push notifications by creating and uploading an Apple push certificate (p12 file) to your push application record in ServiceNow.
    • Optionally test push notifications using out-of-the-box configurations.
    • Optionally set up deep and universal links by downloading and uploading the associated AASA file to enhance app navigation.

    3. Approve or reject the app

    • After testing, either reject the app to revise branding or configurations or approve it to proceed with publishing.
    • If rejected, use the Duplicate option to create a new app request with existing details for easier updates.

    4. Customize your app's workflows

    Use ServiceNow’s Mobile App Builder to tailor the app’s workflows, ensuring the app meets your organization's specific needs and enhances user experience.

    5. Publish and distribute your app

    • Complete your Apple App Store listing in App Store Connect, including metadata and privacy information.
    • Submit the app for Apple’s final review before it becomes publicly available on the App Store.
    • For any publishing issues, file a Now Support case.

    6. Keep your app updated

    • Update your app at least once per year or before updating your ServiceNow family version to maintain push notification functionality and access the latest mobile features.
    • Refer to ServiceNow documentation for supported devices and versions.

    Learn the next steps to test and publish a new branded iOS app for public distribution after you request it in Mobile Publishing.

    1. Test the app

    After the build successfully completes and your app is ready for testing:
    1. (Optional) If you use Microsoft Intune mobile application management (MAM), Microsoft requires that iOS apps be registered with Microsoft Entra ID before anyone can log into the iOS app. For more information, see the following ServiceNow® Knowledge Base articles:
    2. Navigate to the Request details page by selecting All > Mobile Branding > Manage Mobile Publishing Apps > Your recent app requests.
    3. Select the card for your mobile app build request. The Request details page appears.

    4. Select the iOS testing file link and the file is downloaded to your local system for testing:

      Mobile Publishing UI showing the testing file download link

    5. Provision the app by doing the following:
      1. Create an app ID and distribution certificate.
      2. Edit and sign the XCArchive file.
      3. Use XCode to upload the app to the App Store Connect.
      See KB0997467 for step-by-step instructions.
      Note:
      Don't miss the walkthrough video ("Video Walkthrough.mp4") that is attached to KB0997467. It contains a lot of helpful information.
    6. Your testers receive an email from Apple TestFlight with a link to test your branded app.
      Note:
      You must add your testers to a TestFlight group on your AppStoreConnect account and then publish the TestFlight build to the testing group. Only after you perform these steps, do your testers receive an email from TestFlight.

      Use TestFlight to check the following:

      • App has the correct name, icon, splash screen, branding, and theming. For morning information, see Create a theme with Theme Builder.
      • 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.

      See Apple documentation for information about using TestFlight.

    2. Set up the app

    After your Testflight testers have validated the branding and functionality of your app, you can set up your app for use. These configurations are optional.
    1. Set up push notifications by downloading the Apple push certificate (p12 file) and uploading it to your app's push application record:
      1. Create your push notification certificate (p12 file). For instructions, see KB1506609. When you perform this step, you create a push certificate password that you must use in Step 1c. below.
      2. Access the Push Applications table on your instance by navigating to All > Push Application.
      3. Configure your push applications. For instructions, see Configure push applications for iOS branded apps using certificate based authentication.
      4. (Optional) Test your push notifications by using out-of-the-box configurations. For more information, see KB0829093.
    2. (Optional) Set up deep links and universal links for your app by downloading the universal links file (AASA) in the Your app's info tab under the App info section.
      • See KB1273622 for more information about deep links and universal links.
      • See KB0831613 for information about how to upload your universal link AASA file.

    3. Approve or reject the app

    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 you have rejected the app.
    • Approve the build to move forward with publishing the app to your end users.

    4. Customize your app's workflows

    Use Mobile App Builder to customize your app. See Mobile App Builder for detailed information about how you can customize your branded app.

    5. Publish and distribute your app

    After you have tested your app, set it up, customized its workflows, and approved it, you are ready to publish your branded iOS app for public distribution:
    • Fill out your Apple app store listing on App Store Connect and publish the app.
    • Apple conducts a final review before posting the app to the public App Store. Please file a Now Support case for any issues.
    For instructions:

    6. Keep your app updated

    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.