Best Practices and Troubleshooting

This information helps you implement recommendations and troubleshoot when using Mobile Publisher.

Setup for Mobile Publisher is available in Lightning Experience only. However, admins can switch to Lightning Experience from Salesforce Classic to manage the branded app lifecycle.

Recommendations

Mobile Publisher for Experience Cloud

• URLs that share a domain, but have different paths are treated as internal domain URLs and open inside the Experience Cloud site as a WebView.
• Experience Cloud users can be restricted from using the Experience Cloud app through connected app settings. See Manage Access to a Connected App for more information.
• Avoid using custom components for viewing or downloading files such as images or PDFs. Use the file reader provided by the mobile operating system (Android or iOS) to view files by tapping directly on the image or PDF.
• Submit a beta app request after you know the final Experience Cloud site URL.
• Use the final branded App Name in a test project since the App Name gets tied to the Experience Cloud site URL.
• Use CDN for content storage and distribution that’s geographically closer to your users. CDN changes the URL for the Experience Cloud site.
• Avoid using pop-up windows or new tabs in the Experience Cloud site, because they aren’t optimized for mobile apps.
• To ensure no last-minute changes to Experience Cloud site URLs, work closely with your site admins.
• Experience Cloud site admins should avoid making any URL changes after the Mobile Publisher for Experience Cloud app is live.
• For orgs with multiple Experience Cloud sites, deep linking to other sites can cause issues.
• Google Chrome blocks the download of files and content from insecure sources (HTTP). Ensure that your files or content is fully migrated to HTTPS to protect your users and to avoid any issues.
• Use a sandbox or UAT environment for testing.
• Use standard components for logout.
• Only enable the Manage mySalesforce App permission for admins or specific required profiles.
• When you create a site for testing in a sandbox, ensure that the underlying technology is the same as the site in production. For example, if your production site uses an LWR template, your sandbox site must use the same LWR template. And if your production site uses an Aura template, the sandbox site must use the same Aura template.

• Testing
  This information helps you troubleshoot when testing Mobile Publisher apps.
• Authentication
  This information helps you troubleshoot authentication issues when using Mobile Publisher.
• De-list or Remove Apps from App Stores
  Learn how to temporarily remove apps from app stores or decommission apps that are no longer being used.
• Suggestions to Prevent App Store and Play Store Rejections
  Keep these suggestions in mind to help prevent Apple and Google reviewers from rejecting your iOS and Google Apps.
• Mobile Publisher for Experience Cloud Best Practices and Troubleshooting
  Here’s some best practices and troubleshooting when using Mobile Publisher for Experience Cloud.
• Known Issues and Limitations for Mobile Publisher
  Learn about known issues for Mobile Publisher.