Articulate Support - “Cannot Access Content” error when launching a course in Articulate Mobile Player

Search for a topic:

Mobile
“Cannot Access Content” error when launching a course in Articulate Mobile Player

You may encounter the following error mesage when attempting to launch Storyline content in the Articulate Mobile Player app for iPad:

Cannot Access Content:

Articulate Mobile Player cannot access this content.

Please review the following reasons and solutions for this error:

You no longer have access to a content item hosted in Articulate Online

If you're attempting to view content that is hosted in Articulate Online but your permissions have been revoked for that content item, you'll encounter a "Cannot Access Content" error. Please contact your Articulate Online administrator for assistance.

Your LMS or web server requires users to login to view content

Currently, there isn't a way to pass security credentials from a web browser to a mobile application apart from Tin Can API. As a result, you won't be able to view SCORM, AICC, or web content in the Articulate Mobile Player if your LMS or web server requires users to login.

To avoid the "Cannot Access Content" error, do one of the following:

Publish your Storyline content for LMS, but do not mark the box to Use Articulate Mobile Player on iPad. (If you include the HTML5 option when publishing, your content will launch in mobile Safari when viewed on an iPad.)
Or, publish your Storyline content for Web, and mark the box to Use Articulate Mobile Player on iPad. Then upload the published content to a web server that does not require users to login to view the content.

Your LMS does not support Tin Can API private content authorization

If you're hosting Tin Can API content in your LMS (rather than an external server) but your LMS doesn't yet support private content authorization for mobile apps, you'll encounter a "Cannot Access Content" error when attempting to launch the content in the Articulate Mobile Player. Use either of the following options to correct it:

Host your published content on a server that is separate from your LMS, and modify the Launch URL in the published output so it can communicate with your LMS. Click here for details.
Or, ask your LMS provider to support Tin Can API private content authorization for mobile apps. Our white paper on Tin Can API implementation provides helpful information.

See also:

Was this article helpful?