---
schema_version: "1"
id: 382760e09509dad6cdbbece0dd997f0ae43ee2d74e2318e888ffa92f6557b67a
title: Submit the App for Approval
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/s1_branded_apps_submit_approval.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.s1_branded_apps_submit_approval.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e0c25ee4307af3898f2b53dcc2459b74314f4bb2f72f757d4d0b80d21b1b246a
description: After testing of the beta version of your app is complete, the next step is to submit the app to the application stores for approval.
products:
  - Mobile App
  - Cross Cloud
release: "264"
---
# Submit the App for Approval

After testing of the beta version of your app is complete, the next step is to submit the app to the application stores for approval.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Setup for Mobile Publisher available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Setup for Mobile Publisher available in: production only (not sandbox)</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in Lightning Experience in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d2513e64">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d2513e64 ">To create and modify a Mobile Publisher project:</td>
            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2513e64 ">Manage mySalesforce Apps</td>
          </tr>
        </tbody>
      </table>

When you submit your app for approval, Salesforce sends the final apps to Google Play and the App Store. Google and Apple review the apps to make sure they adhere to the application store guidelines. Although you’re about to submit the apps in Salesforce, they aren’t immediately available in Google Play and the App Store.

1. From Setup, enter Mobile Publisher in the Quick Find box, then select **Mobile Publisher**.
2. Click **Continue** next to the listing for the iOS app.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-mysalesforce-264-0-0-production-enus/a39debb4-ddcf-4d21-ae97-ca8229316d3a/images/icon_note.png)
    
    Note To make edits, click the **Make Changes** button. On the App Information page, you can upload revised brand assets or change the values in the fields. Then follow the same steps again: Request a new managed package, install it, and request a beta to verify the changes. The **Make Changes** button is available only after a beta app or live app is delivered.
3. Click **Submit App**.
4. To confirm that you’re ready to submit the apps, select the checkbox.
5. Click **Submit App**.
    
    Salesforce submits the app to the application store. It can take anywhere from 1 day to 2 weeks for the store to review and approve your app. During that time, you can’t make any changes to the app.
6. Repeat the same steps for the Android app.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-mysalesforce-264-0-0-production-enus/a39debb4-ddcf-4d21-ae97-ca8229316d3a/images/icon_important.png)

Important For Android private distribution, the BETA status is misleading and not related to providing a beta app to testers. To make the app available for testing, the app status must be in LIVE status.

If there’s an issue during the approval process, Google and Apple can reject the app. If the app is rejected, Salesforce emails you and lets you know exactly how to resolve any issues.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-mysalesforce-264-0-0-production-enus/a39debb4-ddcf-4d21-ae97-ca8229316d3a/images/icon_note.png)

Note For apps distributed with the Binary Upload distribution method, we recommend that you release app updates to your users in a staggered rollout when the update includes any new features. A staggered rollout gives you more flexibility in pausing or rolling back an app update if any issues are discovered in the early phases of the release. See [Release a version update in phases](https://developer.apple.com/help/app-store-connect/update-your-app/release-a-version-update-in-phases/) in Apple Developer Documentation and [Release app updates with staged rollouts](https://support.google.com/googleplay/android-developer/answer/6346149?hl=en) in Play Console Help. 

You can stagger your app update rollout by the percentage of app users. For example, you can start rolling out the update to 1% of users and then 5% of users. If no issues are discovered, you can incrementally increase the percentage. 

We also recommend against rolling out an app update before a weekend or holiday, so that any issues can be addressed quickly.