Prerequisites for Mobile Publishing
Summarize
Summary of Prerequisites for Mobile Publishing
Before submitting your first branded app request using ServiceNow Mobile Publishing, you must prepare your environment by meeting specific ServiceNow instance configurations and obtaining necessary third-party accounts. These prerequisites ensure that your instance and tools are ready to support building, testing, and distributing mobile apps effectively.
Show less
ServiceNow Instance Requirements
- A cloud-connected production instance is mandatory to request a Mobile Publishing build. The resulting mobile app build can then be used on any one instance.
- The Mobile Publishing plugin (com.glide.sn-mobile-whitelab), a paid plugin available from the ServiceNow Store, must be installed on your production instance.
- Your instance must be configured to allow downloading specific file types (zip, apk, p12, aab, xcarchive, svg, png) necessary for mobile app builds and assets. This is managed under System Properties > Security in the Attachment limits and behavior section.
Third-Party Prerequisites
Private Distribution
- Google Firebase account: Required to generate Firebase App ID, API Key, and Project ID, and to enable push notifications for Android apps.
- Apple Business Manager (ABM): Needed to obtain Apple DEP ID/Org ID and distribute private iOS apps. Ensure the "Custom Apps" setting is enabled in your ServiceNow instance to publish iOS branded apps into ABM.
- Names and email addresses of iOS app testers.
- Apple TestFlight account: Required to test iOS apps, though not mandatory for initial branded app request submission.
Public Distribution
- Google Firebase account: Same requirements as private distribution for Android app notifications.
- Apple Connect and Apple Developer accounts: Required to test, upload, and distribute iOS apps publicly.
- Managed Google Play account: Required to upload and distribute Android apps publicly.
- XCode software (Mac): Necessary to compile iOS branded applications for public distribution.
- Microsoft Entra ID app registration: Required for iOS Microsoft Intune mobile apps starting in the second half of 2024 to ensure successful login flow. Failure to register apps will cause Intune login failures.
Note: For public distribution, some accounts are not required to submit the branded app request but are essential to complete the app 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:
- Navigate to .
- Scroll down the page to the Attachment limits and behavior section.
- 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.
- 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 Azure AD) 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:- Microsoft website explaining the requirement and the timeline.
- Microsoft Entra ID App Registration Mandate for iOS Intune Mobile Apps - Mobile Publishing (KB1640759). (You must have an account and log in to view this ServiceNow KB.)
* These items are not required to request the branded app for public distribution, but they are required to complete the process.