Published course does not display Launch in Articulate Mobile Player option
Apr 29, 2020
This is a new issue for me.
Previously I had published a course with the AMP player options enabled and hosted it on my web server. When a mobile user tried to access the course from a link I provided they would see a banner at the top of the screen asking if they wanted to install the AMP (or Launch the course in the Player if they already had it)
In a recent republishing of the same file with the same publish options, loaded to the same web server the user no longer sees the banner and the course simply plays in the browser.
The story.html file is not detecting the user is on a mobile device and rerouting to the appropriate file.
I can use a workaround by sending a link to the amplaunch.html file instead but then the user ONLY has the option to play in the AMP.
What is going on? Is this a bug in the generated HTML? I have tried in both mobile Safari and Chrome for iOS with the same results.
6 Replies
sample file
https://integration.gpehosting.com/decker/amptest/
I have the same issue. Device is an iPad.
No matter what I do, it always just plays the ocurse and never gives an option to download to Articulate mobile Player.
Trying with chrome and mobile safari and nothing works. I've published all different configurations: Scorm 1.2, Scorm 2004, Tin Can and AICC.
It just never wants to give the option to download.
The only way I'm able to get the Open with Articulate Mobile Player page was to use Storyline 2. Not a typo that's 2.
Hi Randall,
I just responded to a similar question here.
Hi Dan,
In summary of the post I linked above, I was able to track down an open issue we are investigating specific to the Articulate Mobile Player and iPadOS 13+.
Are you using iPadOS version 13 or higher as well?
Hi Leslie,
Yes. iOS 13.3.1.
Is there an ETA on when we should expect an update that will resolve the issue?
Thanks!
Hi Dan,
Thank you for confirming those details! While I don't have an ETA just yet, I will be sure to share your comments with our team. You are in the right place and we will be sure to provide an update on this as soon as we can!
I was experiencing the same thing and opened up a support case on 2/13. It was acknowledged by Articulate support to be a bug. I worked around it just like Randall by making amplaunch.html our launch link as 95% of our audience is users running iPads with AMP installed. But it does mess things up when you want to send out a single link to cover users that want to access your module from a different platform.
Still hoping for a fix! And a new AMP for 2021.
This discussion is closed. You can start a new discussion or contact Articulate Support.