Storyline 3 course published as HTML 5 only but includes one .swf file

I am currently updating all our courses to S/L 3 and publishing as HTML5 only. But when I upload the SCORM package to our LMS, I get the following message

"This content is not supported! The content package you just uploaded contains Adobe Flash files. Adobe has already announced the end-of-life (EOL) for Flash and many browsers are already blocking or removing Flash compatibility and support. We recommend removing this content and republishing it to HTML5. "

The only offending file in the package is a single .swf file. It is our logo which (I'm guessing) is from our logo in the player and that is just brought in as a .png file. It appears in the "mobile" folder along with a .png of the logo. Is there a way to not have that published as a .swf?

9 Replies
Ashley Terwilliger

Hi Andy,

Our team is looking into that bug currently, and we're also working to remove all Flash dependencies from Storyline later this year. 

You can safely delete the SWF file from your published output as a workaround in the meantime. 

Out of curiosity, can you tell me what LMS you're using? I haven't heard of that messages in an LMS yet, so I'd love to know! 

Michelle Gallen

Hi,

A file I'm working on also has a .swf included in the HTML5 only output, which prevents it from being uploaded to the LMS.

I've pinpointed the issue to a .mp4 video which the lesson needs - I can't delete it.

My published output does NOT work if I remove the .swf from the folder.

What is the suggested fix in this case?

NOTE: I've spent a LOT of time troubleshooting this bug. How far up your 'fix list' does it come in terms of priority?

Leslie McKerchie

Hello Michelle and welcome to E-Learning Heroes :)

Thanks for reaching out and sharing what you are running into with your HTML5 output.

The issue above is specific to a logo, and it sounds like you've narrowed yours down to an .mp4 video.

With your permission, I'd like to take a look at your project file to investigate what's happening. You can share it publicly here, or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.

Kimberly Valliere

I'm having and have had the very same issue as Michelle. SL3 randomly throws a .swf file into published output when publishing as html5 only and there's a video present (.wmv file) in the course. I published the package earlier today, no .swf file. Had a very minor change to make to the notes, published again and now there's a .swf file. Team members have also reported the very same problem. The .swf file is only 1KB, so probably not even a swf file, but our LMS balks at the notion. Deleting the file from the folder doesn't work either because the file is listed in the LMSmanifest document and changing that structure is also no bueno for the LMS.

Leslie McKerchie

Hi Kimberly,

Thanks for reaching out and letting us know that you're running into a similar issue. 

I was not able to locate a case for Michelle, so I do not have any additional information to share specific to her example.

We do have this issue reported to our team. Another user mentioned the same issue with being unable to delete due to being referenced in the manifest, so I am making an additional note in our report, updating the impact, and attaching this conversation so that we can update you here when we can.

Michelle Gallen

I'm still here, and I still have the problem. I've deleted the videos and the zooms in the source file, but still get a random .swf in the published file. It's 1kb. LMS refuses to take the published output with a .swf. The published output breaks if I delete it. 

I'm not sure what you mean by a case - nobody asked me to log anything anywhere official - as far as I was aware, open discussions like this are the only way to seek help for bugs.

I can't share my source file with you (it's confidential).I suspect this problem is happening more frequently than is being reported here - are you able to replicate it or is it not being investigated because we can't share our confidential files with you?

Leslie McKerchie

Hi Michelle, 

In my reply to you above, I shared a link where you could share your file with us so that we could take a look. Since you cannot share the file, perhaps that's why the communication ceased.

No worries, we are aware of the issue and tracking user impact. This conversation is attached as well so that we can share any updates with you here.

With regards to how to get support, I'd like to share our Support Policy with you. We do have the community forum discussions with a staff presence, but you also have direct access to our support engineers to work privately here.