Forum Discussion
SOLVED: Storyline block not allowing mobile users to exit
Hi all,
I created a course in rise that uses quite a few SL blocks. The problem I'm having is that, when accessing this course in Articulate Review from my iPhone, once I click the 'Play' button on the block, I'm unable to return to the Rise page. When activated, the SL block maximizes on my window and I am unable to see any of the other content in the Rise lesson. I tried swiping in all directions, but the SL block takes over the screen as if it's a lightbox with no exit button. Has anyone had this experience? Did I make a mistake building the SL block? Any advice would be helpful.
**EDIT: Solution below
Thanks!
-Trenton
- stevecicciCommunity Member
Has there been any solution for this that can be posted? Thanks.
Hi, Steve. We weren't able to replicate this behavior yet in our testing. Would you be able to work with us and privately share your files for testing? We'll delete everything when we're done troubleshooting. Let us know what browser you're using and where your content is hosted.
Thank you!
- CraigSumner-890Community Member
Hi Trenton, I have seen this before, and found that sometimes the cross to close the content did not show.
I found it was dependant on the rotation of my phone or the browser I was using.
I never really solved this, as we ended up removing our storyline content as I found a way to produce what I needed with one of the Rise Blocks.
- TrentonIrons-64Community Member
Thanks! That did the trick for one of the modules, but the other still won't show me the 'X'. They both happen to be the same SL block size (medium). I'll open a ticket and post the resolution in this thread in case anyone else runs into the same issue.
- TrinaRimmerFormer Staff
Thanks for posting the question and for sharing any subsequent findings with others, Trenton. Sorry you've run into a challenge here, but hopefully, you'll get some answers from our support team!
- TrainingTeam-04Community Member
I'm having the same issue. Unable to find an 'X' regardless of screen rotation. Hitting the back button on my phone takes me back to the very beginning of the Rise course. Ugh. (Tested this on both a iPhone 8 and a Samsung Galaxy S9+.)
- TrentonIrons-64Community Member
Hi there,
The support team gave me a solution. They stated that it appears to be a software bug with the modern player. It was found that if you change the player from modern to classic in your Storyline block (then re-publish and re-select the block within Rise), you won't have those issues.
- NicoleLegault1Community Member
Thanks for taking a moment to share the solution you used, Trenton! Glad this was resolved for you.
- DanPriceCommunity Member
I'm experiencing this issue too but thankfully have found this thread. Annoying having to republish a number of Storyline interactions but at least it's a workaround.
I'm guessing a proper fix will be developed in time?
Thanks
- NicoleLegault1Community Member
Hi Dan,
So glad this thread has been helpful! Our team is monitoring this issue and we'll share any updates and/or fixes here.
Please reach out if we can help with anything else.
- VctorGmezCommunity Member
I've found this same issue. Unfortunately I cannot use the stated workaround as the storyline blocks are to be used from many platforms (pc, android...) and the classic player brings out other different issues. Are you planning to solve that bug on Iphone with modern player soon?
Hey, Victor. I don’t currently have any updates, but you are now subscribed to this conversation which means as we share updates here, you’ll automatically be notified.
- SimonBertoli-9bCommunity Member
Hi All
Late to the game here but I am having this issue, not on the initial viewing of the SL block but when its revisited. The exit X button does not show.
It is published in the classic player.
Can anyone else verify this behaviour?
Hi there, Simon. We released a fix in Storyline update 27 for this behavior. If that Storyline interaction was published before May 2019, please publish it again and add the block back to Rise 360 to see the fix.
If it's been published after that fix, let us know! We'll dive in and find out what's happening. You can reference this discussion for context.