Stealthray.swf Security Issue with Studio 09 and Flash Player 10

Hi,

I have been using Articulate since 2008 and remember an issue with previous versions of Articulate Presenter that caused issues while playing published courses on browsers with Flash Player 10.

I know the problem was fixed with the Updater and Studio 09 was built to tackle this problem. I haven't faced this problem since 2009. However, strangely enough,my reviewers encountered this error while trying to view a course published using Studio 09 and on a browser running Flash Player 10. 

--

Adobe Flash Player has stopped a potentially unsafe operation.

The following local application on your computer or network:

<link to local drive where the publised output folder is placed\stealthray.swf>

is trying to communicate with the Internet-enabled location:

<link to local drive where the publised output folder is placed\player.html>

To let this application communicate with the Internet, click Settings.

You must restart the application after changing your settings.

---

I need a global fix to this issue as I have to share the course with a team of reviewers located globally before the course goes live.

Please help!

~Sam

14 Replies
Justin Wilcox

Hi Sam,

If you are having people reviewing content for you that will eventually be online, test the content online. Testing Flash content offline that attempts to communicate with the internet is considered a security threat and treated as such. Testing content offline does not provide any real world analogy for how something will work online so I would avoid it if at all possible.

Samarpan Dutta

@Steve Thanks for your suggestion. After reading your post, I did publish the course to CD output but see that the player folder still contains a "stealthray.swf" file. Wondering if it'd still cause the same issue as before.

@Justin I understand your logic. But, in our firm, content goes "online" only after the content has been reviewed by SMEs and  finalized. Then it is tested online for technical issues and goes live for learners. So, still wondering what to do.

Also, really surprised at the recurrence of this issue after Articulate Presenter 5. I have never encountered this issue before with Articulate Studio 09.

Thanks, guys!

Sam

Justin Wilcox

Hey Sam.

I would suggest having a sandbox or testing or staging site on your web server. Things need to be tested online. Not necessarily in a live production area but most companies nowadays have testing areas for authors. If yours doesn't, you should ask them to. Testing Flash content offline, nowadays, simply doesn't work. Yes, you can publish for CD but it's not going to give you an apples to apples comparison of how the content works online.

It sounds like you need to have an honest conversation with your web server folks so you can move testing to where it really should be. I don't know of a legitimate reason why people should be forced to test content that doesn't work offline, offline.

I can honestly say that people testing content offline is one of the top reasons people contact support because the content doesn't work as expected.

Steve Flowers

Hey Sam,

Nope. That won't cause the same issue in a CDROM publish. The reason you see that error in the browser is due to the browser security sandbox defaults. The CDROM launcher still launches the HTML output. There may be some issues that differ from online deployment and you won't see the same load times, but for the most part there is parity between the CD publish and online publish, in my experience.

Justin Wilcox

Hi Lynn and welcome to Heroes. See this article. As I indicated earlier in this thread, you should test content published for an LMS in the LMS, not offline to ensure it is working correctly. If you wanted to view content locally there are a variety of ways to do that. You could publish for CD, you could use Dropbox as a web server and publish for Web. That being said, to truly test your content you should test it exactly where you plan on hosting it.

Peter Anderson

Welcome to Heroes, Elaine!

As long as you host the content in the environment for which it was published, those you share the course with should have no trouble viewing it, assuming that their Flash players are up to date. So for example, if you'd like to share your course with your affiliate who does not have access to your LMS, you can publish the course for web and simply share it using Dropbox

Sasha Scott

Hmm I am having the same problem, previously when I published for web or LMS and ran a module locally, there was no such message. Now this message appears for all modules (even ones published several years ago that never displayed this message). The only possible answer is that it is a new Flash update issue, likely something to do with enhanced security. Not an Articulate issue as nothing has changed in these modules...

As people have said above, this only applies if you're trying to view it locally - when running the same module off a server, the message does not appear. Suggested solution is to ignore the message (i.e. click OK)