Loading
Mobile Publisher for Salesforce App
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Set Up Environments for a Binary Handoff Project for the Salesforce Mobile App

            You are here:

            1. Salesforce Help
            2. Docs
            3. Mobile Publisher for Salesforce App

            Set Up Environments for a Binary Handoff Project for the Salesforce Mobile App

            Set up Apple and Google environments for binary handoff projects.

            Required Editions

            Setup available in Lightning Experience in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions.
            User Permissions Needed
            To set up environments for a binary handoff project for the Salesforce Mobile app Manage mySalesforce Apps

            Register Apple Identifiers

            Follow these steps in your Apple Developer account to register the required identifiers for your mobile app.

            1. Create two separate Identifiers: a Bundle ID for the main app and a Notification Service Extension ID.
            2. Your identifier name used for Apple setup should be the same Customer Store ID you provided on the Salesforce Setup UI submission form.
            3. When creating the Notification Service Extension identifier, add the Push Notifications capability. Don’t add the Broadcast capability.
              Important
              Important The Store ID supplied within the Mobile Publisher setup UI is for internal use only. Customer Store IDs could be in a format such as: com.{yourcompany}.{uniquename or identification}. Use naming conventions that meet Apple’s requirements.
            4. Create an App Group with a unique name that includes your Customer Store ID.
            5. Both the Bundle ID and the Notification Service Extension identifier must be assigned to the App Group capability. The App Group capability is located on the Identifier, when you edit your App ID Configuration page. Select Edit to choose the App Group created in the previous step.

            Provision Profiles

            Generate a separate provisioning profile for both the Bundle ID and the Notification Service Extension.

            1. Generate a separate provisioning profile for both the Bundle ID and the Notification Service Extension.
            2. In the Profiles section of Apple Developer, select App Store Connect as the profile type.
            3. Select the appropriate App ID from the dropdown menu and link it to the related distribution certificate.

            Set Up Apple Push Notifications (Optional)

            The Apple Push Notification (APNs) key is used during the External Client Apps setup in Step 2 of the Mobile Publisher Setup UI.

            1. Use an appropriate naming convention for your Key, enable the Apple Push Notifications service (APNs), and click Configure.
            2. Select Sandbox and Production from the dropdown menu and click Save.
            3. Select Register, then download the generated key.
            4. Store the keys in a safe and secure location where it remains accessible.
            5. Use this key when enabling push notifications within your External Client Apps for either Production or Sandbox deployments.

            Set Up Google Play and Cloud

            Android apps require specific Service Accounts, JSON keys, and Firebase registration details to complete the setup.

            1. Ensure you use only your unique Store Identifier for all Google-related configurations.
            2. Create the necessary Service Account in the Google Cloud Console and generate a related Key in JSON format.
            3. Register your app in the Firebase Console to obtain the google-services.json file and the firebaseadminsdk.json.
            4. Upload the google-services.json file during Step 1 of the Mobile Publisher setup form, as it is a required field.
            5. Provide the firebaseadminsdk.json during Step 2 of the External Client Apps setup; this file is optional and only required for push notification configurations.
              Note
              Note Customers planning to use universal links in their Android app must provide the SHA-256 certificate fingerprint. You can locate this value in the App Integrity section (under Setup) within the Google Play Console.
             
            Loading
            Salesforce Help | Article