Forum Discussion
Engage Interaction still generates .swf in Storyline web output
- 3 months ago
Hi, all!
I have some great news to share! We just released a new version of Storyline 360 (Update 102), which included a fix for the issue where SWF files are created after publishing an embedded Engage interaction in Storyline 360.
To take advantage of this update, launch the Articulate 360 desktop app on your computer and click the Update button next to Storyline 360. You'll find step-by-step instructions here.
Please let us know if you have any questions by posting here or reaching out to our Support Engineers directly.
I'll have to see where to find that. My hope is that they'll at least address this one issue with a final update!
Hi MichaelDixon-e1,
We released an update way back on May 4, 2021, that removed all Flash files from Engage 360 interactions. Courses published using the most recent versions should no longer have Flash content included in the published output. Would you be willing to share a copy of your project files here or in private by opening a support case so we can check for any Flash files? We'll delete it when we're done testing!
- MichaelDixon-e13 months agoCommunity Member
Actually, after submitting this to e-learning heroes, I submitted a support request with project files and received a response indicating a team was assigned to the issue. Apparently v.99 of Storyline does behave properly, but other versions seem to generate .swf, so they are working on the issue and potential fix.
Engage indeed is not generating .swf, but when Engage is added to Storyline and a Web output is generated, that's when .swf appears...so it's a Storyline issue.
- StevenBenassi3 months agoStaff
Hi MichaelDixon-e1!
Glad to see Joe has been helping you!
As you mentioned, you've also connected with my teammate Darrell, through a support case. Smart move! As Darrell shared, we have this behavior logged as a bug in Storyline 360. This bug causes .SWF files to be created, and included in published output files when publishing an embedded Engage interaction in Storyline 360.
I've linked this discussion to the bug report so we can notify you as soon as a fix is in place. In the meantime, as a workaround, we suggest downgrading to Storyline 360 version 3.99.34516.0 where this issue cannot be observed.
Thank you for your patience. I'm sorry if this has been slowing you down!
Related Content
- 10 months ago