Thanks for sharing the .story file. I took a look and published it to Review here. That one worked for me on Mac OS - 10.12.6 and 10.13.1 in Chrome and Safari. I also tested it in Safari on iPhone 6S using iOS 10.3. All those worked, and showed the initial play button which is a new feature of Safari.
Let me know how that works for you and what OS exactly you're using (and browser versions)!
Thanks taking a look at my file for me. The link you provided works on my Safari and iPad. I think it's an issue with our server configuration. Today I got access to a second web server to test on, an LMS, and it worked there as well.
One of our more techie people suggested it's related to the content-range response on the IIS/ASP.NET server, and highlighted these 2 bits below. It went a little over my head, what he was saying :)
But for now, we're going to test on the second server, and see what happens when our clients tests it on theirs. I'll let you know how I make out, and if I find out any more information that may be useful to other users.
If you have another server to test on, great! Let us know how it works there. You could also look at testing by uploading to Tempshare for Web content or publishing to SCORM Cloud for LMS content.
3 Replies
Hi Chris,
Thanks for sharing the .story file. I took a look and published it to Review here. That one worked for me on Mac OS - 10.12.6 and 10.13.1 in Chrome and Safari. I also tested it in Safari on iPhone 6S using iOS 10.3. All those worked, and showed the initial play button which is a new feature of Safari.
Let me know how that works for you and what OS exactly you're using (and browser versions)!
Thanks taking a look at my file for me. The link you provided works on my Safari and iPad. I think it's an issue with our server configuration. Today I got access to a second web server to test on, an LMS, and it worked there as well.
One of our more techie people suggested it's related to the content-range response on the IIS/ASP.NET server, and highlighted these 2 bits below. It went a little over my head, what he was saying :)
RESPONSE (APACHE):
Content-Range: bytes 1097728-1126384/1126385
RESPONSE (IIS):
Content-Range: bytes 0-1126384/1126385
But for now, we're going to test on the second server, and see what happens when our clients tests it on theirs. I'll let you know how I make out, and if I find out any more information that may be useful to other users.
Thanks, Chris
It's a bit over my head too, Chris! 🙃
If you have another server to test on, great! Let us know how it works there. You could also look at testing by uploading to Tempshare for Web content or publishing to SCORM Cloud for LMS content.
This discussion is closed. You can start a new discussion or contact Articulate Support.