HTML5 blank in Chrome 48 PC, Chrome 47 Android, Safari iOS, Chrome 47 iOS
Mar 02, 2016
By
Aaron Olson
I am having an issue where the html5 output published as Web (Articulate player for iOS is NOT checked) is working fine on my Samsung Galaxy S5 using the native Android browser. It displays on my PC using IE 11 but the vids don't start and the controls don't appear. However, it appears as just a player frame with blank white content in the following: Chrome 48 on PC, Chrome 47 on Android, Safari on iPad, and Chrome on iPad.
I have read several other threads on the topic and none of them seem to help:
- It appears blank both when I have it set to size to browser window and lock at optimal size.
- It is blank when I publish both as Web and LMS output.
- I downloaded the most recent Storyline 2 update (7) and re-published the project. No change.
- I downloaded the Articulate Updater for Chrome and updated all files it identified on my machine, no change.
- I am putting it on a server where the user does have to enter their credentials before accessing. However, I'm not publishing with the Articulate player for iOS selected (I've never been able to get that player to show my projects on the iPad anyways). It works with the authentication fine on my Android in the native browser. It seems to go to the project fine in Chrome as well, just doesn't display the content inside the player frame.
Can anyone from Articulate help me out? Happy to send a zip of the files, but can't share with the world.
cheers
6 Replies
Hi Aaron!
Yes, I think taking a look would be the best bet. You are welcome to share privately here.
With some help from Miker at Articulate I found the solution to this issue. He published the course on his server and it worked from that link.
Therefore, I did several things:
1. I re-uploaded the exact package of files that I sent to Miker and that were working in the link that he provided me to make sure I was comparing apples to apples.
2. When I navigated to the project, I made sure to first enter the authentication and then enter the url to the project. This way I knew I was already logged in. I don't think this was the issue though.
3. I cleared the cache on each browser I was testing. This is what I think did it.
I believe what was happening was that after I did the Chrome Update/Storyline Version 7 update and republished, the browsers where the html5 wasn't working were still displaying the older cached version of the project instead of the new updated one.
This should've been the first thing I checked since I'm constantly telling clients to clear their cache when they aren't seeing updates in my Flare online documentation. Duh!
Thank you for your help!
Glad to hear that you were able to get everything working and I appreciate you popping in to share your explanation/solution with the community :)
Aaron,
IE11 seems to be the worst for me, where I often have to delete all my temp files to get it to refresh a Storyline project. My solution has been to place very specific versioning text on my first slide, which I update every time I re-publish. This way I know for sure that I'm looking at the correct version in the browser.
Thanks,
Mike
That's a good tip Mike!
I hope it helps someone. :) It just takes a second to update the number, and has saved me a lot of headaches where one of my browsers suddenly decides to cache an old version of the page, where it was working fine before that.
This discussion is closed. You can start a new discussion or contact Articulate Support.