Prerequisites for Mobile Publishing

  • Release version: Australia
  • Updated March 12, 2026
  • 2 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 Prerequisites for Mobile Publishing

    To successfully submit your first branded app request using Mobile Publishing, certain prerequisites must be established in your ServiceNow instance. These prerequisites ensure that your instance is properly configured for mobile app creation and distribution.

    Show full answer Show less

    ServiceNow Instance Requirements

    • A cloud-connected production instance is necessary to request a Mobile Publishing build.
    • The Mobile Publishing plugin (com.glide.sn-mobile-whitelab) must be installed, which is a paid plugin available from the ServiceNow® Store.
    • Your instance should support downloading specific file types: zip, apk, p12, aab, xcarchive, svg, and png. Ensure these are included in the static content download settings under System Properties > Security.

    Third-Party Prerequisites by Distribution Type

    Private Distribution Prerequisites

    • Access to a Google Firebase account for generating necessary keys and setting up push notifications.
    • Access to Apple Business Manager (ABM) for generating IDs and distributing private iOS apps. Enable the "Custom Apps" setting in your instance.
    • Names and email addresses of your iOS app testers.
    • An Apple TestFlight account, required for completing the testing process.

    Public Distribution Prerequisites

    • Access to a Google Firebase account for app ID generation and notifications.
    • An Apple Connect account for testing your iOS app.
    • An Apple Developer account for app upload and distribution to the public store.
    • A Managed Google Play account for Android app distribution.
    • XCode software on Mac to compile iOS applications for public distribution.
    • Microsoft Entra ID app registration for iOS Intune mobile apps, required by Microsoft starting in the second half of 2024.

    Note that while some of these items are not strictly required to request a branded app for public distribution, they are essential for completing the publishing process.

    Before submitting your first branded app request with Mobile Publishing, it's important to set up some prerequisite tools.

    ServiceNow instance requirements

    Regardless of the distribution method or app provider that you choose, your ServiceNow instance requires the following configurations to use Mobile Publishing:

    • A cloud-connected production instance is required to request a Mobile Publishing build. Once you have the Mobile Publishing build, you can use the mobile app on any single instance.
    • The Mobile Publishing plugin (com.glide.sn-mobile-whitelab) must be installed on your production instance. The Mobile Publishing plugin is a paid plugin that can be installed from the ServiceNow® Store, see Install a ServiceNow Store application

    • Instances must be able to download the following file types: zip, apk, p12, aab, xcarchive, svg, and png.

      To add file types that can be downloaded by your instance:

      1. Navigate to All > System Properties > Security.
      2. Scroll down the page to the Attachment limits and behavior section.
      3. Make sure the zip, apk, p12, aab, xcarchive, svg, and png file types are included in the file types that can be downloaded as static content from an instance.
      4. Select Save.

    Third-party prerequisites by distribution type

    Make sure that you have the following third-party applications to request, test, and publish branded mobile apps.

    Private distribution prerequisites

    To request a branded app for private distribution, you must have access to the following:

    • Google Firebase account
      • Generates the Firebase App ID, Firebase API Key, and the Firebase project ID.
      • Sets up push notifications to Android devices.

      For more information about Google Firebase, see the Google Firebase documentation.

    • Apple Business Manager (ABM)
      • Generates the Apple DEP ID/Org ID and the org name.
      • Distributes private iOS apps.
      For more information about Apple Business Manager, see the Apple Business Manager User Guide.
      Important:
      Be sure to enable the "Custom Apps" setting in your ServiceNow instance. This enables you to publish the iOS branded apps into ABM.
    • Names and email addresses for your iOS app testers.
    • Apple TestFlight account, which is used to test your iOS account.
      Note:
      The Apple TestFlight account isn't required to request a branded app for private distribution but is required to complete the process.
    Public distribution prerequisites

    To request a branded app for public distribution, you must have access to the following:

    • Google Firebase account
      • Generates the Firebase App ID, Firebase API Key, and the Firebase project ID.
      • Sets up push notifications to Android devices.

      For more information about Google Firebase, see the Google Firebase documentation.

    • * Apple Connect account, which is used to test your iOS app.
    • * Apple Developer account, which is required to upload and distribute the app to Apple's public store.
    • * Managed Google Play account, which is used to upload and distribute your Android app.
    • * XCode software (Mac), which is required to compile the iOS branded applications for public distribution.

    • * Microsoft Entra ID app registration for iOS Microsoft Intune mobile apps.

      Microsoft requires iOS Intune apps be registered with Microsoft Entra ID (formerly Microsoft Entra ID) in the second half of the calendar year 2024. Apps that are not registered will fail the Microsoft Intune login flow. For more information, see the following resources:

    * These items are not required to request the branded app for public distribution, but they are required to complete the process.