--- sourceDocument: Xanadu Mobile Configuration and Navigation sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/mobile Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu Mobile Configuration and Navigation ft:clusterId : - mobile bundleId : - mobile workflow : - Development, Data and Analytics --- # Update a branded app # Update a branded app {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read Request and publish an update to a ServiceNow® mobile app that has been branded with your unique company identity. Updates can only be requested for approved, completed builds of branded apps. ## Before you begin Role required: admin ## About this task Mobile Publishing enables you to request an updated version of your branded iOS or Android app that you can distribute publicly or privately. You can request an update for the following branded app options: * New version of the ServiceNow mobile app. * Requester contact information such as first name, family name, and email address. * Change whether you want to use your custom End-User License Agreement (EULA) and privacy policy or the default ServiceNow EULA and privacy policy. * For iOS apps that use private distribution, you can add or delete testers for [TestFlight](https://developer.apple.com/testflight/) notifications. {#update-branded-app__ul_uqy_dsh_mrb} Important: Only the above information can be changed on completed builds of branded apps. If you must change any other options, you must request a new branded app with Mobile Publishing. ## Procedure 1. Navigate to AllMobile BrandingManage Mobile Publishing Apps. 2. In Your recent app requests section of the page, select the completed branded mobile app build that you want to update. 3. On the Request details page for the branded mobile app, select Duplicate. The Review and submit page appears for the branded mobile app. 4. On the Review and submit form, fill in the following fields to update the app. {#update-branded-app__table_dww_t13_mrb__entry__2} | Field | Description | |-|-| | Your contact info | If the contact for the app has changed, enter the First name, Last name, and Email address for the new requester of the updated branded application. | | Your app's info section | When you're updating a branded app, this information can't be changed. Important: If you must change these fields, you must request a new branded app. | | App name section | When you're updating a branded app, the Short name can't be changed. Important: If you must change the Short name, you must request a new branded app. | | Mobile Application Management (MAM) | Whether you want to use a MAM vendor with your apps. For more information, see [Mobile application management (MAM) integration](https://www.servicenow.com/docs/5TpjO7zcLG~xTQPiZjomqg "Use Microsoft Intune or BlackBerry Dynamics to secure and protect sensitive information in mobile applications, even in cases where customers use their own mobile devices."). To enable a MAM vendor, select the Use Mobile Application Management toggle. | | Mobile Application Management vendor | Select one of the following MAM vendors from the list: * Blackberry * Intune {#update-branded-app__ul_rlg_1gw_gbc} This field is only visible if you select the Mobile Application Management (MAM) toggle. | | End-user license agreement (EULA) and privacy policy | EULA and privacy policy options can be updated or changed. Select the toggle Use ServiceNow's EULA and privacy policy to turn on the default EULA and privacy policy. | | EULA | URL where app users can view your custom end-user license agreement from the mobile app settings. This option only displays when you don't select to use the default ServiceNow EULA. | | Privacy policy | URL where app users can view your custom privacy policy from the mobile app settings. This option only displays when you don't select to use the default ServiceNow privacy policy. | | iOS Universal links/Instances used for deep links Note: If you're updating an iOS branded app, this option is named iOS Universal links. If you're updating an Android branded app, this option is named Instances used for deep links. | This table shows all ServiceNow instances used for your organization. Select the instance URLs that you want to be built into your app as an iOS Universal link or as an Android deep link. If you must configure a link to a URL that isn't listed in the table, select Add custom URL, enter the URL, and then it's added to the table for selection. Note: * This functionality can only be edited when you submit a new branded app request or when you update a branded app. * If you're updating an iOS branded app, you must download the Apple App Site Association (AASA) JSON file after you submit this request and install the file on all instances in the URL list. {#update-branded-app__ul_xb3_x5l_ddc} To learn more about deep links and universal links, see [Mobile URLs](https://www.servicenow.com/docs/3Oxb8vK4wjj_8ISYWH9e0Q "Create mobile URLs to direct users to areas, screens, and features within specified mobile apps. Using mobile deep linking, these re-directional links can be placed within emails, texts, and push notifications."). | | Login management || | Pre-populate instance | Turn on this toggle to build an instance URL into your branded app so end-users don't need to enter the instance URL during login. Enter a default app instance URL that is secure and uses Hypertext Transfer Protocol Secure (https://). Note: * This instance URL can only be added when you submit a new branded app request or when you update a branded app. * Don't select this option if you're using AppConfig to preconfigure a default instance URL through an EMM suite or an embedded MAM SDK app. For more information, see [AppConfig for Mobile Apps](https://www.servicenow.com/docs/Mzk68MhmaO8zSqEv~sv3Rw "Use AppConfig to define a default instance and browser for your managed mobile apps."). {#update-branded-app__ul_gwy_vwl_ddc} | | Default app instance | Enter the secure default app instance URL. This field is only visible if you select the Pre-populate instance toggle. | | Nickname | (Optional) Enter a nickname for the Default app instance URL that displays on the mobile app for your end-users. This field is only visible if you select the Pre-populate instance toggle. | | Icons and splash screens configurations | When you're updating a branded app, this information can't be changed. Important: If you must change these fields, you must request a new branded app. | | Internal iOS app testers (iOS only) | If you're updating an iOS public or private branded app, you can change the First name, Last name, and Email address of the tester. | [Table 1. Request new branding form] {#update-branded-app__table_dww_t13_mrb} 5. Select Submit. ## Result After you complete the request form and submit it, your ServiceNow instance builds the updated branded app. When it completes, you receive an email notification about the status of the build. A link is provided from where you can download the app file. Note: * You can only submit one build at a time. You can't submit another build until the current build is canceled, failed, or completed. * Check the following table for estimated times to build your updated branded app. {#update-branded-app__table_ubd_gyl_ddc__entry__3} | App operating system | Public distribution | Private distribution | |-|-|-| | iOS | 1 week approximately | 2--4 weeks \* | | Android | 1 week or less | 1 week or less | [ ] {#update-branded-app__table_ubd_gyl_ddc} \* Privately distributed iOS apps must be inspected by Apple's human reviewers and can take 2--4 weeks until they're ready for testing. If you are on a tight timeline, submit your privately distributed Android app first so that you can test it while you submit and wait for the iOS app build to complete * ServiceNow can't expedite delivery timelines because they're determined by Apple or Google. {#update-branded-app__ul_um1_rxl_ddc} ## What to do next After the build successfully completes, select one of the below topic links to test and publish your updated branded app. * **[Test and publish an updated Android app for private distribution](https://www.servicenow.com/docs/nUd272zYYxoI3nafV0fpEw)** After you have requested an updated Android branded mobile app for private distribution, perform these steps to test and publish it. * **[Test and publish an updated iOS app for private distribution](https://www.servicenow.com/docs/~GQ2uVd8IkcnV5pA9JZ0fw)** AFter you have requested an updated iOS app for private distribution, perform these steps to test and publish it. * **[Test and publish an updated Android app for public distribution](https://www.servicenow.com/docs/n~Uk8uxXadjRnQ68n5DMYw)** After you have requested an updated Android app for public distribution, perform these steps to test and publish it. * **[Test and publish an updated iOS app for public distribution](https://www.servicenow.com/docs/1Txt~Xw5XlI01kLgT2wCMQ)** After you have requested an updated iOS branded mobile app for public distribution, perform these steps to test and publish it. *[\>]: and then