Known Issues and Limitations for Mobile Publisher

Mobile Publisher

• You can’t identify and send email notifications to Mobile Publisher admins. Email notifications go to all your system admins.
• You can create hyperlink formula fields for iOS and Android. But Android doesn’t support:
  • HYPERLINK("https://salesforce.com", "Salesforce")
  • HYPERLINK("https://salesforce.com", "Salesforce", "_blank")
  Android does support:
  • HYPERLINK("https://salesforce.com", "Salesforce", "_self")

  See Tips for Working with Hyperlink Formula Fields for more information.

Mobile Publisher Login Webview Limitations

• You can’t add a custom domain within the Login page. You can add custom domains by using the gear icon in the container to add a custom server.
• Lightning Login pages, using *.lightning.com domains for login, opening a link in an external webview, pop ups, outbound universal links, app links, and custom schema aren’t supported.
• Login pages must have a unique URL. Mobile Publisher currently doesn’t support login page URLs that popup in a separate window.
• Intermediate authentication URLs, such as multi-factor authentication (MFA) verification pages and external identity provider (IdP) pages for SAML, don’t need to be added to URL Management. If intercepted during login and not configured in URL Management, these URLs automatically open within the login screen on both Android and iOS, allowing authentication flows to complete without interruption.

Custom URI Schemes and Deep Linking

• Custom URI schemes (such as kotak://, ibl://, or myapp://) used for outbound deep linking to external native apps require configuration in the Allowlist Custom URL Schemes field in Mobile Publisher Setup for Android or iOS. If not configured, these links fail with ERR_UNKNOWN_URL_SCHEME because UUM routes non-HTTP/HTTPS schemes through the in-app WebView or browser, which can’t handle them.
• Non-HTTP/HTTPS schemes such as tel:, mailto:, and maps: can fail on iOS Publisher apps if UUM routes them to the in-app browser. Test these links thoroughly and configure them to open in an external browser in URL Management.
• For known issues related to custom URI schemes and UUM, see Known Issue: Custom URI Scheme Deep Links Fail with ERR_UNKNOWN_URL_SCHEME After UUM Rollout. If you encounter this issue, contact Salesforce Support.

Mobile Publisher for Experience Cloud User Authentication Limitations

• Advanced deep linking authentication isn’t supported. For example, a logged-in user taps on a link and is automatically authenticated to another site or portal. Mobile Publisher doesn't support this example or any other type of biometric encryption to achieve advanced deep linking authentication.
• If guest users can access parts of your site, include on those unauthenticated pages a link to the default login page URL. Doing so allows guest users who want full access to your site to log in and authenticate. Don’t link directly to SSO.
• Salesforce doesn’t support unauthenticated API access. As a result, for unauthenticated users, only publicly accessible files are available for download.

Mobile Publisher for Experience Cloud Other Limitations

• Downloading Lightning Knowledge articles isn’t supported, but downloading Classic Knowledge articles is supported.
• The Mobile Publisher app doesn’t pass authentication to other sites or apps.
• Mobile Publisher for Experience Cloud apps don't support Salesforce Tabs and Visualforce templates.
• Some self-registration flows aren’t supported. Make sure to test your flow in the Playground app first. It’s recommended to register new Experience Cloud users in a web browser on desktop or on a mobile device. Users can log in to the app after completing their registration.
• When setting up your site in Experience Builder, configure your site’s registration page to load from the app’s login page because both registration and login require authentication. You can configure the same page to show either registration or login using different URL parameters. For example, the parameter /login?register=true shows the registration page and hides the login page, while /login?register=false hides the registration page and shows the login page.
• Downloading CRM Analytics dashboards and reports isn't supported on Mobile Publisher for Experience Cloud apps.
• Mobile Publisher for Experience Cloud apps don’t support dark theme or dark mode on Android and iOS devices.
• Mobile Publisher for Experience Cloud sites doesn’t support iframe integration. If your app includes the iframe element, your app users can experience functionality issues.
• 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.

Registration

During the new user registration workflow of an Experience Cloud app, workflows that require passing information from the Experience Cloud app to an external app, and then back to the Experience Cloud app aren’t supported. For example, if an app user receives a confirmation email with a link to continue in the Experience Cloud app, the Experience Cloud app can’t continue the workflow using a universal link or app link transition. Similar workflows for forgotten passwords or resetting passwords also aren’t supported.

We recommend that forgotten password, password reset, or email confirmation workflows during registration are completed in a web browser, rather than completed in the Experience Cloud app.

For example, to prevent a registration workflow from being handled in email, you can modify the assetlinks.json (Android) or apple-app-site-association (iOS) file of your app to exclude links sent through email. For instructions on how to modify these files, see Override Android App Links to Your Mobile Publisher App and Override iOS Universal Links to Your Mobile Publisher App.

Note The information in Override Android App Links to Your Mobile Publisher App and Override iOS Universal Links to Your Mobile Publisher App applies only to Salesforce domains (for example, examplesite.site.com).