I have Storyline courses I am putting on iPads for a class, and using the Mobile Player in class. Once the content is downloaded onto the iPads, I remove it from the server. They have been working for about two years this way. I had to update two of the three courses in Storyline 2. I click to download the content, test, and they work fine until I remove the files from the server. I have updated the player and the iOS to 10.2. It seems as if the content must not really download, although I watched it go through the process. The one course that I did not update still works fine. I really need to get this working asap before the next class.
I wouldn't expect it to have worked if the courses were removed from the server - as that is where the Articulate Mobile player was pointing to load the courses from. If they were set for offline, and you had downloaded them as such - they'd play while you were offline even if they had been removed from the server but once you connect to the internet again the app is going to try and communicate with your server and therefore the course won't load as it's no longer accessible.
Sorry I can't think of another option to get around this behavior for you - but hopefully having clarification on the expected behavior will help you proceed.
They were set for offline and downloaded. This is how we have been doing it for a couple of years. So you are saying that now if we connect to the Internet, the player will try to load them again instead of playing the downloaded files?
Correct - and that's what I'd expect to happen once you reconnect to the internet. So if they're removed from the servers, they are no longer accessible. Is there a reason you need to delete them?
AMP works with content published for Tin Can API if you need users to log into a course from an LMS, as that allows the ability to pass the credentials and tracking information back and forth. Did you publish for LMS and choose SCORM, as that may not be allowing it to access the AMP. You could publish for Web and that should bypass that. We're also on update 11 of Storyline 2, so it's always a good idea to ensure you're on the latest update.
7 Replies
Hi Emily - Is this content that you are loading and allowing for offline viewing via the Articulate Mobile Player or another system?
Yes, we are using the Articulate Mobile Player. We have been using it for a couple of years this way, and I just made a small update to two courses.
Hi Emily,
I wouldn't expect it to have worked if the courses were removed from the server - as that is where the Articulate Mobile player was pointing to load the courses from. If they were set for offline, and you had downloaded them as such - they'd play while you were offline even if they had been removed from the server but once you connect to the internet again the app is going to try and communicate with your server and therefore the course won't load as it's no longer accessible.
Sorry I can't think of another option to get around this behavior for you - but hopefully having clarification on the expected behavior will help you proceed.
They were set for offline and downloaded. This is how we have been doing it for a couple of years. So you are saying that now if we connect to the Internet, the player will try to load them again instead of playing the downloaded files?
Correct - and that's what I'd expect to happen once you reconnect to the internet. So if they're removed from the servers, they are no longer accessible. Is there a reason you need to delete them?
Yes - they are not intended for public use and AMP does not accommodate logins. Now I am having issues with it not recognizing that AMP is installed. Same as the issue in this link, but with Storyline 2 Update 10 and iOS 10.2. https://articulate.com/support/article/articulate-storyline-1-content-wont-launch-in-the-articulate-mobile-player-on-ios-9-devices#existing
Hi Emily,
AMP works with content published for Tin Can API if you need users to log into a course from an LMS, as that allows the ability to pass the credentials and tracking information back and forth. Did you publish for LMS and choose SCORM, as that may not be allowing it to access the AMP. You could publish for Web and that should bypass that. We're also on update 11 of Storyline 2, so it's always a good idea to ensure you're on the latest update.
This discussion is closed. You can start a new discussion or contact Articulate Support.