I tested your file using iOS 13, and noticed the same thing! You can't exit out of the course by clicking the button.
Without seeing the actual .story file, I'm thinking it must be a trigger we can change! I'm happy to investigate. Would you mind sharing your .story file with us? You can do so by using the "add attachment" button in this discussion.
It looks like the Storyline course didn't come through. Could I have you resend the .story file? You can include it with your comment by using the add attachment button here:
Also, it looks like your email signature came through when you replied via email. You can remove it if needed by clicking ‘Edit’ beneath your response. Here’s a quick video if you need help!
Perfect, that's it! I've tested multiple triggers and state changes to have a better understanding of this snag. You've stumped me!
I've started a case with our Support Engineers who are the right people for the job! They'll test your file and share their findings via email. I'm interested in the outcome so I'll be following along too!
Have some content that works perfectly in iOS12, however in iOS13 the previously published (and newly published content) in HTML5 needs the buttons to be double clicked.
Our team is currently looking into this issue further, so I don't have any updates at the moment. In the meantime, a workaround that might help is to remove the Down State of a button:
You are in the right place, and we will be sure to provide updates as soon as we have more information!
Hi all! I had the exact same problem, excapt it was for a picture triggering a layer. I found a link explaining that on iOs first the hover state is activated and only then the click/selected action is activated: https://github.com/angular/components/issues/1316 It is not storyline related, but it is iOs related.
11 Replies
Hi Bart!
I tested your file using iOS 13, and noticed the same thing! You can't exit out of the course by clicking the button.
Without seeing the actual .story file, I'm thinking it must be a trigger we can change! I'm happy to investigate. Would you mind sharing your .story file with us? You can do so by using the "add attachment" button in this discussion.
You bet. When I run from our LMS, it will close fine from a Mac or PC but on the iPhone/iPad, you need to click the button twice to close.
I’ve attached the SL file.
Thanks for investigating!
-Bart
Hi Bart,
It looks like the Storyline course didn't come through. Could I have you resend the .story file? You can include it with your comment by using the add attachment button here:
Also, it looks like your email signature came through when you replied via email. You can remove it if needed by clicking ‘Edit’ beneath your response. Here’s a quick video if you need help!
Thanks. Here's the attachment.
Hi Bart!
We'll actually need the .story file which you can find on your local drive. Sorry for the hassle!
Doh!
Hi Bart!
Perfect, that's it! I've tested multiple triggers and state changes to have a better understanding of this snag. You've stumped me!
I've started a case with our Support Engineers who are the right people for the job! They'll test your file and share their findings via email. I'm interested in the outcome so I'll be following along too!
Is there an update on this?
Have some content that works perfectly in iOS12, however in iOS13 the previously published (and newly published content) in HTML5 needs the buttons to be double clicked.
Thanks.
Hi Micahel,
Our team is currently looking into this issue further, so I don't have any updates at the moment. In the meantime, a workaround that might help is to remove the Down State of a button:
You are in the right place, and we will be sure to provide updates as soon as we have more information!
Hi all! I had the exact same problem, excapt it was for a picture triggering a layer. I found a link explaining that on iOs first the hover state is activated and only then the click/selected action is activated: https://github.com/angular/components/issues/1316 It is not storyline related, but it is iOs related.
Removing the hover state worked for me.
Hello Everyone!
I'm happy to return to this discussion with an update—we've fixed the issue where:
Be sure to install the latest Storyline 360 Update 52 to take advantage of all the recent features and fixes.
If this happens again, please let us know! Or you can work directly with our support engineers here.