I work for an eLearning company. Today we have a considerable number of users who can no longer play our Flash courseware. These users are running the Flash Player version 22 released yesterday, June 16. We can replicate the problem in IE11, Edge, FireFox and Chrome. OS tested include Windows 7, 10, and Windows 10 running in a VMware install on a Mac.
The courseware plays as expected with Flash Player version 21. With Flash Player version 22, content does not display. With Flash Player version 22, we can view other Flash content, for example, http://www.timeticker.com.
Sample of Flash content that does not display running Flash Player version 22:
Any help towards a remedy for this would be most appreciated.
Adobe Flash Player 22.0 - Bug 4165783
Thanks for reporting the issue.We are looking into it.
We will update you.
We're working on the issue.
In the meantime, it if really is the same content, the following workaround may be useful to you:
Wrap the upMask with an if statement on line 294
upMask(w,h); // Update mask (Price:0.1ms)
I unfortunately do not have access to the source code nor a Flash authoring environment.
We have the same problem. I installed the debug version of flash and using the log file I received the following error when accessing your url:
Error: Request for resource at xmlsocket://127.0.0.1:1978 by requestor from http://ces.puresafety.com/CMS_Content/testFlashPlayer22/testFP22/engine/Version_1_5_1/giantBrain.swf is denied due to lack of policy file permissions.
I got the same error when trying to access our content.
Is there a resolution for this?
Copy link to clipboard
many, many thanks to you and your team for your efforts
Will Flash player beta 184.108.40.206 be pushed out for Chrome, and how soon? After several attempts to uninstall Flash Player and install Flash player beta 220.127.116.11, Chrome does not seem to want to use 18.104.22.168. 22.214.171.124 is not listed in chrome://plugins
Flash player comes embedded with chrome. You can not use beta build on chrome.
It will be available in our next scheduled release.
Many thanks. What is the timeframe for the next scheduled release?
Flash Player ships on a monthly schedule, typically aligned with Microsoft Patch Tuesday. We ship one major version, followed by two patch releases, so we tend to increment a major version every 3 months.
In terms of our decision making, updating 2.5 billion users isn't easy. Simply rushing fixes into the player often leads to problems that are worse than the thing we were originally trying to fix. The major versions get the most exposure to the beta channel audience (several weeks vs. 1-2 for a patch release), so we tend to align risky fixes to the next major version to ensure both that the fix works, and that we didn't introduce side-effects that break other developers.
I can certainly relate to updating 2.5 billion users. Admittedly, our user base is on a much smaller scale, however, dealing with the several thousands of users who cannot play their courseware since the Flash Player 22 release on June 16 has been, to say the least, extremely challenging. We're a pretty big shop (UL) , with pretty big user base, and those users are all aware and waiting for an Adobe fix for the side-effects that broke the courseware they spent their training budgets on.
126.96.36.199 is a beta-only build. Whatever is included in 188.8.131.52 would be included in the next scheduled release of Flash Player. Regularly scheduled released of Flash Player occur on the second Tuesday of the month.
Thank you, Kratika, for all your efforts, helpfulness, and patience. We're very much looking forward to 14 days from now.
As an aside, if Flash Player is central to your business, we'd strongly encourage you to use our beta builds for regular testing.
While we have an extensive set of automated tests, supported by a small army of people that perform manual testing and tend to the automated systems, we have finite resources. The fast pace of evolution and fragmentation in the OS and Browser space makes maintaining those tests and systems challenging, and there are always some gaps in the existing coverage at any specific point in time.
At the same time, we're continuously hardening Flash Player in the face of an increasingly sophisticated adversary. Flash has been around long enough to see the transition from script kiddies to world class state-sponsored engineering groups, and as a ubiquitous client software with a much larger footprint than any individual browser, Flash is a high-profile target for attackers looking to maximize their investment in exploit development in terms of both reach and client configuration.
We work closely with academic and industry partners to stay ahead of the curve to the extent possible, engaging in both proactive and responsive work, in consultation with some of the brightest people and security engineering groups in the OS and Browser spaces. We're absolutely committed to consistently and aggressively responding to security issues, and to further hardening the player.
The unfortunate problem is that we're frequently forced to make invasive changes for which the side-effects are not always readily apparent. We test extensively, but there are limits that stop short of perfection. While we work really hard to try and not break existing content, the scale of the existing corpus of Flash content on the web and all of the potential client player combinations makes for a combinatorial nightmare.
In light of those constraints, we offer the beta program to empower developers with mission-critical Flash deployments the ability to supplement their own testing with advanced copies of forthcoming releases. We take beta feedback very seriously, and to the extent possible, prioritize newly injected issues to make sure that bugs that break existing content never ship to the general population. Timing is important there, and the earlier we know about an issue, the more likely it is that we can get it taken care of (i.e. filing a bug a day or two before we ship would probably not result in a good outcome -- we're already locked and loaded).
We post mostly-weekly builds (we'll skip if the beta build isn't worth testing, or for boring logistical reasons), and we have dedicated forums for beta feedback. You're also more than welcome to send me a direct private message to me, and/or any of the staff that you see regularly here, in the event that you have something to escalate. Seriously, I want to know about that kind of stuff right away, and you're more than welcome to ping me directly. If you file a detailed bug and send us the bug number with the note, that's even better, as we can route it directly to someone for triage.
Beta Builds: http://www.adobe.com/go/flashplayerbeta
Discussion Forums: http://forums.adobe.com/community/labs/flashruntimes/flashplayer/
I just wanted to mention that we totally appreciate that this has been a painful and frustrating experience, and sincerely apologize for the headache. I think we've all been on the other side of it. You've been very cool about it, and we very much appreciate your patience.
Good morning, Jeromie
Thanks very much for taking the time, good sir. Very kind of you. We're all in this together
We're on track to release the next update (184.108.40.206) on July 12th. You should see this start appearing over the next 12 to 24 hours.
Thank you very much to everyone @ Adobe!
No problem. As a friendly reminder, please, please, please, test with our betas on a regular basis. If your content breaks, let us know ASAP. Feel free to file a bug, and send me and/or any of the regular staff that post here a PM to get it expedited.