Has anyone recently experienced problems running content through Google Chrome for mobile devices on Android?
I'm hosting storyline 2 modules on a custom built LMS with no problems (so far). However, recently when they are launched on Google Chrome on Android devices they appear to launch, the audio on the opening slide plays, I can access the resources and volume control within the player but no visuals are displayed. I just get a blank white screen within the boarder of the player, nor can I navigate to the next slide.
This seems to have started happening since a recent Google Chrome update in mid September.
They still work fine on other web browsers.
I would be greatful for any advice or ideas why this might be happening.
At first I thought it was a problem with the videos, but it looks you are right. It depends the length of the video and therefore the time the user is idle looking at it.
No solution has been provided yet, but I have a ticket open for it.
Hi Alistair! Looks like Marc has popped in to share his related issue.
I took a look at Marc's case to understand the issue and these do seem similar. If you are utilizing Chrome 45 on your Android device, this is exactly what has been reported to our QA Team.
The only workaround that has been listed is to utilize Articulate Mobile Player (AMP) when viewing the course in Android devices.
Yes, these issues are probably related. But using AMP is not a solution. You can't force people to install an app on their device to just view a bunch of html5 content that should work flawlessly.
There is something to fix in the html5 output of storyline or there is a bug to fix in chrome and some others browsers on android.
It's started from android chrome 45 release and was wokring before. If I had access to un-offuscated readable js code generated from storyline I could at least try to debug what is causing this. But the generated js code is unreadable....
Is there is no news from your developpers about the progress on this issue ? Is that such a big problem to fix ??
4 Replies
Hi,
Seems it's related to the same problem I posted here:
https://community.articulate.com/discussions/articulate-storyline/audio-problems-with-html5-since-latests-chrome-updates-on-android
At first I thought it was a problem with the videos, but it looks you are right. It depends the length of the video and therefore the time the user is idle looking at it.
No solution has been provided yet, but I have a ticket open for it.
Cheers,
Marc
Hi Alistair! Looks like Marc has popped in to share his related issue.
I took a look at Marc's case to understand the issue and these do seem similar. If you are utilizing Chrome 45 on your Android device, this is exactly what has been reported to our QA Team.
The only workaround that has been listed is to utilize Articulate Mobile Player (AMP) when viewing the course in Android devices.
Yes, these issues are probably related. But using AMP is not a solution. You can't force people to install an app on their device to just view a bunch of html5 content that should work flawlessly.
There is something to fix in the html5 output of storyline or there is a bug to fix in chrome and some others browsers on android.
It's started from android chrome 45 release and was wokring before.
If I had access to un-offuscated readable js code generated from storyline I could at least try to debug what is causing this. But the generated js code is unreadable....
Is there is no news from your developpers about the progress on this issue ? Is that such a big problem to fix ??
I do not have an update at this time Marc, but the QA Team is aware and working on this. This thread is flagged for update when applicable as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.