You are here:
Limitations for Mobile Publisher for Experience Cloud LWR Sites
Experience Cloud sites are built on one of two frameworks—Lightning Web Runtime (LWR) or Aura. Each framework supports specific templates. Mobile Publisher for Experience Cloud supports all Aura templates and the Build Your Own (BYO) LWR template. Some limitations apply only to apps created from LWR sites. If your users need features that aren’t available with the BYO LWR template, use a site built with an Aura template instead.
These Mobile Publisher limitations apply to apps created from LWR sites and enhanced LWR sites.
Templates and Components
- You can use only the Build Your Own (LWR) template.
- A limited number of standard Lightning components are available. To get more features and functionality, build custom Lightning components.
- Sites hosted on Experience Delivery aren’t supported.
Logout Flow
The default logout flow, in which users are directed to your site login page at logout, isn’t available. And you can’t create a customized logout experience. Instead, manually add a Logout link in your site header that points to /secur/logout.jsp. The code in logout.jsp redirects to the Salesforce login page (login.salesforce.com).
Authentication
Multi-factor authentication workflows aren’t supported in apps created with Mobile Publisher for the LWR platform.
Navigation
In Experience Builder, the features in the Additional Navigation Options section () are available only for Aura sites on the Customer Account Portal, Partner Central, Customer Service, and Help Center templates. The additional navigation options aren’t supported in apps created from LWR sites.
Notifications
- Mobile Publisher for apps created from LWR sites supports notifications and
routing notifications to the appropriate targets. However, the standard bell
component that shows the count of all unread notifications isn’t available for
LWR sites. As a result, the standard in-app bell icon component for
notifications isn’t available on apps created from LWR sites. To include a
notifications bell icon in your app, build a custom Lightning web component that
uses the Notifications
API. A custom component that uses the Notifications API also marks
notifications as read, which enables an app’s badge to show the correct count of
unread notifications. When used with a Mobile Publisher app, the Notifications
API supports both standard and custom notification types.
Tip For an example component that uses the Notifications API, see Notification Bell for Experience Cloud (LWR) in AppExchange. To view the open-source code for the example component, see salesforce-experiencecloud/notificationbell in GitHub. - Custom Lightning web components and the Aura notifications component within a Mobile Publisher app don’t support polling. Without polling, the notifications component shows new notifications only when the app is refreshed.
Other Limitations
- Messaging for In-App and Web isn’t supported.
- 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.
