Forum Discussion

JoeBurgett's avatar
JoeBurgett
Community Member
3 years ago

"Access Denied" error on Canvas Page using iOS (safari and app) with Storyline 3

I use storyline 3 to publish my presentations to my class using Canvas as the LMS.  My presentations work great using a web browser on my laptop or desktop PC.  However, when I try to view them on an iOS (multiple apple devices), there is a message on canvas that says "Access Denied."  When I try to view the page where the presentation is located using the Canvas app, it just shows a blank page.  I've attached a screenshot of the same Canva page; one from my laptop and the other from my iPad.

 

A lot of my students want to use their apple products for class but right now I don't have a solution for them.  Please help!!!

  • JoeBurgett's avatar
    JoeBurgett
    Community Member

    Actually CLemson's  IT folks figured it out.  I pasted their response below.  It fixed the issue completely:

     

    There is an option in Safari on iOS devices called "Prevent Cross-site Tracking" that is enabled by default. I assumed this might be the underlying issue so I tested it on my iPhone and disabling the option allowed my to open the link you sent. You can access this option by going to Settings->Safari->Privacy & Security on your iOS device. You could also download a different browser (Chrome) on your iOS device and it would fix the issue as well.

  • Hello Joe, 

    Glad to help! 

    To isolate if the issue is specific to when your courses are hosted in Canvas LMS, try accessing your course using iOS devices after hosting them on a different LMS such as SCORM Cloud. Here's a helpful guide on how to troubleshoot your course in SCORM Cloud: 

    If the behavior only occurs when accessing your course in Canvas LMS, reach out to their support team for further assistance. If your course will not load in SCORM Cloud as well, open a support case with our team so we can take a closer look at what's happening. 

    Let me know if you have any questions! 

  • Hi Joe,

    Thanks for updating this thread with your findings! I'm glad to hear you solved the issue. If you run into any trouble moving forward, please let us know here or privately in a support case if you prefer!