Recently I've been seeing a considerably higher number of 3320 errors when using a Flash Access enabled player on MacOS. I'm aware that the documentation lists 3320 as a Generic Internal Flash Access error, but I'd like to provide anything diagnostically useful as well.
These errors occur in a point in the playback process
1. After the Flash Access Runtime has been successfully installed
2. After the content metadata has been loaded and successfully parsed (no 3343 or 3344 errors thrown as part of that)
3. As the ActionScript code is calling mDrmManager.loadVoucher(mDRMMetadata, LoadVoucherSetting.FORCE_REFRESH);
4. Reviewing data from an HTTP Proxy indicates that the request for the license is never made.
I can reproduce the problem consistently with:
flash MAC 11,2,202,229
Firefox 11 - Flash Player 188.8.131.52
Safari 5.1.5 - Flash Player 184.108.40.206
We did have a bad module for Build 220.127.116.11 on Mac OS 64-bit. Perhaps you 'cached' that bad module.
If you look at finder in:
See what library you have down there. Most likely you have the one that was corrupted. (adobecp64-301806-1.plugin).
Also, we've updated the player to build 233. Maybe it's just best you upgrade your Flash Player and it should re-download the (newer, clean) DRM modules
18.104.22.168 also has a corrupt module that tested OK internally. We're refreshing this today.
Did this get pushed? The current version of FP for MacOS is still 22.214.171.124.
If the new runtime was pushed, will the old versions see 3343/3344 events and update accordingly?