Built in player buttons not appearing in the responsive player

Mar 10, 2017

I'm hoping someone could help me. 

I have a module built in storyline 2 but upgraded it to 360. It uses the built-in player for the next/back and submit buttons, which work perfectly on desktop and in the old mobile player, but in this new responsive player the buttons appear invisible on certain devices. The buttons haven't disappeared completely, after a lot of clicking I found they're still at the bottom of the screen and work fine, other than the fact they're invisible. 

It seems you can't edit any of the features on this player, so I'm really stuck when it comes to finding a solution. Is anyone else having this issue or know of a fix?

I've attached a screenshot to help illustrate. 

5 Replies
Alyssa Gomez

Hi there Emily! Thanks for letting us know what you're seeing! Which mobile devices are giving you this trouble? Are you using a supported mobile browser to test the content (Safari in Apple iOS 8 or later, Google Chrome in Apple iOS 8 or later, Google Chrome in Android OS 4.1 or later)? Have you also tried testing a brand new Storyline 360 file in the same environment? 

I'd be interested in getting a copy of your file so I can test it on my end. You can either share it here in the forums, or send it directly to our Support Engineers if you'd rather share it privately. 

Crystal Horn

Hi Emily!  I just wanted to add a thought here.  It looks like you're using the Articulate Mobile Player, based on your screenshot.  We've identified an issue where the navigation buttons are missing from that output on certain devices:

  1. Nexus 7 running 6.0.1 AMP version 4
  2. Acer Iconia Tab 8 A1-840FHD running 4.4.2 AMP 4
  3. Lenovo A3300-GV Android 4.4.2 AMP 4

Can you confirm the device type where you're seeing this behavior?  We're working with our team to investigate where the breakdown is occurring!  In the meantime, if you don't need to make the content available offline to your users, you can uncheck the box to include AMP when publishing, and the new responsive player (based on the mobile device browser) should display the content well, all navigations intact.

We'll be sure to update this discussion when we get more information on this issue!

This discussion is closed. You can start a new discussion or contact Articulate Support.