Forum Discussion
Content overlaying in mobile devices with blocks
Hello,
I've created a Rise course and embedded a Storyline block with the Modern player and the controls off.
In Rise, when learners complete the block I made the Continue button appear. The problem is that in mobile devices, the new content overlays with the block, and it is almost impossible to close the block, as the close 'X' button is difficult to click.
Storyline version is updated.
Any solution with this?
Thanks
Hi everyone, 🎉
I'm happy to let you know we released a new update for Rise 360. This update fixes the issue you encountered where learners could play a Storyline block and scroll through lesson content simultaneously. There's nothing to install for web apps. New features and fixes are immediately available, though you might need to export your Rise 360 course again.
Let me know if you have any questions about this update or the issue you reported!
Hi Proveedor 1!
It sounds like you're having trouble viewing a Storyline Block on mobile devices!
I see that you've also opened a support case that's being handled by my teammate, Janina. It looks like Janina replied to your e-mail requesting a share link to your course. You're in great hands troubleshooting with her and we can continue the conversation through your case.
Hi, having similar issues with storyline blocks in Rise on mobile. Once a storyline block has been selected you can still scroll content over the top of the storyline block and you can select continue. Then the storyline block remains open in the background. It seems like the storyline activated window area is at the back layer of all the content which causes issues. This seems to be a new issue which didn't happen before the Rise UI update. Please fix!
Hi HP Life!
Sorry to hear you've run into this setback!
Testing the behavior on my end, I was able to replicate the same issue. We are currently tracking this bug in Rise 360, and I've included your voice in the report. We'll be sure to update you as soon as a fix is in place.
Thank you for your patience. Sorry if this has been slowing you down!
Hi Steven, I'm having the same issues with Storyline blocks in Rise on mobile (the X button behaves very erratically, either doesn't display, or is very hit and miss whether it works - when it does the Storyline content is still visible behind the Rise content). I've been trying to figure out what the problem is for the last two weeks!
This is a significant issue for my team, we use Storyline blocks in all our Rise courses and are not currently able to confidently publish any courses. We are a large team of 25 designers releasing courses frequently, so are very urgently awaiting a resolution to this issue.
Hi Rowan,
Thanks for sharing what you see on your end. Your experience sounds similar to what others have reported in the existing bug. I'll add the bit about the X button in the bug report and inform our team regarding your post.
We'll update this discussion if anything changes, and you'll be among the first to know!
Hi Eric, thank you, appreciate your quick response.
You're welcome, Rowan! Enjoy your weekend ahead.
Hi everyone, 🎉
I'm happy to let you know we released a new update for Rise 360. This update fixes the issue you encountered where learners could play a Storyline block and scroll through lesson content simultaneously. There's nothing to install for web apps. New features and fixes are immediately available, though you might need to export your Rise 360 course again.
Let me know if you have any questions about this update or the issue you reported!Hi, thanks for the fix but there now seems to be another issue. When using pinch zoom on a storyline block in Rise on mobile you are now confined to the small storyline block frame area. You can't then zoom into all areas of the storyline block content which is an issue especially when viewing on a mobile phone in portrait. When you pinch reduce zoom after zooming in you cannot see the full storyline block area (which hides buttons at base).
Hi, I have worked out that the zoom issue was a bug in the latest storyline application update. I have had to install a previous version which seems to have fixed it.
