Skip to main content
December 15, 2015
Answered

Flash 20.0.0.228 inside MFC C++ is now showing as blank screen

  • December 15, 2015
  • 3 replies
  • 1352 views

Hi,

Recent update to Flash v.20.0.0.228 (ActiveX) used in C++ Application that was working until this update is not working anymore, now is just showing a blank screen.

Debugging the app didn't throw any error in any case (with all exceptions turned on in MS VS).

This is happening in all calls to .swf with all our applications (200+) in all clients (a lot) that ran the update.

Tested in several machines with Windows 7 to 10, new update 100% fails and old one 100% success. Seems nothing to do with SO.

Example:

Rolling back to flash v. 19.0.0.245, it runs correctly:

Thanks in advance,

Carlos

This topic has been closed for replies.

3 replies

December 16, 2015

*to upper replies: Thank you, but don't think its the same issue here. And i think its fairly easy for you to reproduce now we managed ourselfs to get where the problem is and get it working with a workaround.

We did a rollback in our code and detected that if we rollback a patch applied to secure the policies enforced some versions ago (more than 1 year) by Adobe to use "file://" before the file location in order to safely access to file while invoking CShockwaveFlash::LoadMovie the movies started loading again.

Removing that "file://" from the path, we get the swf file movies loaded, but that change in this update is a drawback in security on Flash Player 20:

Regards,

Carlos Nogueira

ivanp61579321Correct answer
Participating Frequently
December 17, 2015
December 17, 2015

Thanks Ivan.

Participating Frequently
December 16, 2015

Hi,

Thanks for reporting the issue.

Could you please verify if your issue is same as issue reported on below link:

https://forums.adobe.com/thread/2036049

jeromiec83223024
Inspiring
December 16, 2015

The most expedient path to a resolution is to reproduce the bug with a C++ debugger attached.

To that end, please file a bug at http://bugbase.adobe.com/.  Please include detailed instructions on how to reproduce the issue.

If you post back here with the bug number, I'll get a notification and will open it to the engineering team for further investigation.

Thanks!