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

You can publish the course to CD output to get around the local security sandbox issue. This basically includes an extra file that wraps the HTML in a player. Using this publish method you won't see any of these errors.

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.

@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

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.

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.

What about Apple users? They can't open a .EXE file

I had to deliver a corporative eLearning course on DVD (due to the client's decision). My workaround was a big warning sign on the label of these DVDs: "PC users: click on CourseName.EXE. Apple users: click on CourseName.html

Favio, there is no real work around for apple users, your solution is the only real one

hi

i am getting the stealthray error, however, I am publishing to the LMS option and not a CD. Anything I can do here, or have I done something that's causing this error?

thanks

Hi Yuna,

Would you like to submit a case so we can get more information on the issue?

I am seeing the same issue as yuna B. I'm publishing to the LMS option. Do you have any suggestions of what to do?

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.

Hello.  I am encountering the same issue.  I can get the content to launch, after dealing with the error messge, but how do I avoid the same problem e for others?  We need to share a course via web with an affiliate that does not have access to our LMS.

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. 

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)