-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VPAIDFLash.swf doesn't work #208
Comments
The issue is when the reference to I wonder if this is a security ('https') issue |
Any solution to this? |
Make sure Flash is installed |
@rushanq do you get any network errors? Did you check if the paths of the generated swf object is pointing correctly? |
Also, you might try compiling the 'bin' files from scratch by cloning the repo. The files that are currently committed don't appear to be generated from the latest source. |
The latest source appears to be working for me |
@lpender I will try compiling from source. Also flash is installed if not then why its running Vpaid Swf creative when VPAIDFlash.swf is local and not on a CDN.
The only thing that changes is vpaidPath |
@lpender rebuilding from source fixed the issue. Its working now. Thanks a lot |
@rushanq fyi, after more extensive testing, I realized that the ads still fail with this message intermittently on the latest build. I narrowed the issue down to a race condition in VPAIDFLASHClient: MailOnline/VPAIDFLASHClient#17 Fwiw, the problem can be solved by hardwiring FlashTester.isSupported to return true. |
@lpender the flashTester is async by nature since is doing the following: So if you are playing a video in autoplay or "too soon" will not use flash in the first play. If is this what is happening, then I can had a feature to by default assumes that flash can play (if swfobject test pass and in the background really test if is true or not) more details: #182 |
We where having this problem when opening up the html file directly without hosting it via file://. Once we hosted it on a local server it worked perfectly. |
Is there a way to kill this flash loader dependency? Flash is pretty much dead thankfully. |
I have the same problem. |
I have the same issue. not always working in production, it fails for many browsers. |
I am using similar code both for development version (where VPAIDFlash.swf is located locally) and production version (VPAIDFlash.swf on a server - nginx as reverse proxy). I am able to play Flash based creative locally but not in production version. It gives
AD ERROR: VAST Error: on VASTClient.getVASTAd.validateAd, could not find MediaFile that is supported by this video player i {message: "VAST Error: on VASTClient.getVASTAd.validateAd, co… MediaFile that is supported by this video player", code: 403} [a]
Only thing that has changed is the path of VPAIDFlash.swf.
Even tested the same behaviour on Amazon S3 :( any solution
The text was updated successfully, but these errors were encountered: