Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Unsupported Visualforce Components

Here’s a list of Visualforce components that aren’t supported in the Salesforce mobile app, and shouldn’t be used in Visualforce pages that will be used with the Salesforce mobile app.

<analytics:reportChart>
<apex:detail>
<apex:emailPublisher>
<apex:enhancedList>
<apex:flash>
<apex:inputField> for field types that use a widget for input, instead of a basic form field
<apex:listViews>
<apex:logCallPublisher>
<apex:relatedList>
<apex:scontrol>
<apex:sectionHeader>
<apex:selectList> for picklist fields
<apex:tabPanel> (and, as a consequence, <apex:tab>)
<apex:vote>

Embedded Visualforce pages—that is, those added to a page layout—that contain an <apex:enhancedList> component may cause the Salesforce mobile app to crash on iOS.

Warning

Standard components outside the apex namespace, for example, <liveagent:*>, <chatter:*>, and so on, aren’t supported in the app.

Custom components can be used in Visualforce in the app, as long as they themselves don’t use unsupported components.

Visualforce Developer Guide

Unsupported Visualforce Components