Known issues

This section describes the known issues in SDL Tridion Mobile Simulator.

Handling of Dynamic Component Presentations
Problem: You need to have your Component included statically on a Page to use Mobile Preview of the Component. In other words, you cannot preview mobile content if you are using Dynamic Component Presentations.
Solution: Use a placeholder Page and select the Allow on Page check box in your Component Template.
Notification of items in Publish Queue
Problem: When you select Mobile Preview in Content Manager Explorer or SiteEdit, a publishing action is performed. As items can wait a while in the Publish Queue before being published, it would be useful to receive notification when an item has been published, and provide a refresh option, so you can see the changes.
Solution: Open the Ribbon toolbar Home tab and click Publishing Queue to view the status of items that have been published.
Scope of the publish action is not clearly stated in the Message Center
Problem: The scope of the publish action is not clearly stated in the Message Center. For example, if you have only added your parent Publication to a Publication Target but not the Child Mobile Publications, the Message Center will state that the Component/Page has been set to be Published.
Automatic Publishing switch
Problem: When you select Mobile Preview in Content Manager Explorer or SiteEdit a publishing action is performed, and the action is repeated when you switch Publications. It would be preferable if the preview first shows your current Page state and provides a Publish icon in the Ribbon toolbar so that you can republish the Page, and that you could configure automatic Publishing when you switch to Mobile Preview (in the Metadata Schema which you can add to a Publication to override the Staging Web site, or Netbiscuits Web site, you want to point at).
Netbiscuits ID and Application Name stripped out of Link URLs
Problem: When you configure Mobile Simulator to access Netbiscuits using the Default URL, the Netbiscuits Custom Application Developer ID and Application Name are stripped out of Link URLs. For example, if you click the following link in Mobile Preview: http://apps.netbiscuits.com/1215394/MySite/Welcome.xml it becomes http://apps.netbiscuits.com/Welcome.xml, resulting in a 404 error. (Where 1215394 is the Developer ID and MySite is the Application Name of the NetBiscuits Custom Application.)
Solution: Configure Mobile Simulator to use the Friendly URL of the Custom Application, not the Default URL.