Flash Player 23 update frequent RSL issue

Question

We have a custom flash application that has frequent issues with downloading the rsl files from adobe. This is the message that is logged in the policyfiles.txt log file:

Searching for <allow-access-from> in policy files to authorize data loading from resource at https://fpdownload.adobe.com/pub/swz/flex/4.5.0.20967/framework_4.5.0.20967.swz by requestor from https://mydomain/assets/fonts/swf/myfont.swf

If this file already exists in the local assetcache folder - it may hang on the next file:

OK: Searching for <allow-access-from> in policy files to authorize data loading from resource at https://fpdownload.adobe.com/pub/swz/tlf/2.0.0.232/textLayout_2.0.0.232.swz by requestor from https://mydomain/assets/fonts/swf/myfont.swf

If this file also exists in the local assetcache folder - the application functions properly. If we remove both the cached files - the application will hang during the load most of the time. We have tested using Windows 10 x64 with the latest browser version IE 11, Edge, FireFox 49, Chrome 53 using flash player 23. We have also tested with Windows 7 Pro x64 using IE 11, FireFox 49, and Chrome 53. If we uninstall flash 23 and reinstall flash 22 - the application works and does not generate the log entries. We are doing all our troubleshooting with the debug versions.

The application is a swf file that loads these font swf files. We have many customers using our application that have started reporting this since flash 23.

Any information would be greatly appreciated.

Thanks,

jeromiec83223024 · Answer

All of these files are served directly off the Akamai CDN. While there might be an issue with the individual node that you're routed to, those problems tend to be transitory and very difficult to debug. It's more likely that there's an issue along the route. If you can collect network diagnostics that indicate that the problem is at their node, I can forward them to Akamai for investigation, but historically, that's a slow-moving process.

My recommendation would be to explore hosting those RSLs locally, which would make things more resilient. You can configure your flex application such that if the request for the RSL fails, the client will fall back to your domain for those files.

Adobe Flex 4.6 * Using the framework RSLs

Flex SDK / Wiki / Linking RSLs by Default

We don't revise these very often (the last time was about a year or two ago, when the original signing certificates expired), but if you're self-hosting, you *would* want to set something up to check and sync them periodically to the current versions.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.