I'm creating HTML5 ads for Google Ads.
I created a new set of ads from copied Adobe Animate files that worked fine themselves when zipped and uploaded to Google Ads. The old ads were published using Adobe Animate 2019. These new ads that do not work were published using Adobe Animate 2020.
These duplicated versions are exactly the same, except for some text changes. I publish them, zip them, and upload to Google, and get the following error:
Make sure the filenames of all files in your .ZIP file are exactly the same as the name listed in the reference file. For example, if one of the files in your .ZIP file is called path/to/example/asset, but in your HTML file you reference path/to/example/asset2, AdWords will not be able to to find the correct file. To fix the issue, compare the filename listed above with every file in your HTML5 code. If it is not exactly the same, correct the reference. More details: INVALID_URL_REFERENCE: canvas_
Using search/replace, I see the only file with a reference to "canvas_" is the createjs.min.js file in "/libs/1.0.0/".
The old correctly-working published ads contain a "/libs/createjs-2015.11.26.min.js" file instead of the "/1.0.0/createjs.min.js" file. How do I publish my ad with these same settings instead of the"/1.0.0/createjs.min.js" file? That seems to be the problem here.
Hi, i'm having the exact same problem. It drives me nuts. Luckily for me i had a version of Adobe Animate 2019 on an old MacBook. Hope someone has the answer to this …
Yea, I had to re-install the old version just to finish this project. It's just ridiculous that you can't set default publish settings. I have to manually do it for each of my 50+ ad files.
And I'm sure, even though this is a critical misstep, it won't be a "priority" fix until they feel like it. The drawing/editing tools are an absolute joke. And it's laughable that they still use the ".fla" file format. Talk about putting a bad taste in your mouth—every time I have to double-click one of these files. Don't just re-skin Flash and call it a new product.
Thankfully other programs have been popping up to dethrone Adobe the last few years. We just need an Animate alternative now.
I'm running into the same issue as well - really, really frustrating. As I do not have access to animate 2019 anymore, I am doomed. Would it work to just replace the react.js file with the old one which was generated from the 2019 version or is that file project-specific? If that were possible, could anyone publish the old file here? That'd be amazing!
I'm not sure about a react.js file, but the `/lib` file that worked correctly for me previously was called `createjs-2015.11.26.min.js`. I can't upload a file here, but I've uploaded that `/lib` folder with the js to Dropbox here: https://www.dropbox.com/s/3drtx14sw65khjy/libs.zip?dl=0
Hope that helps.
Thank you very much for your quick help! I've replaced the file and renamed it to the create.min.js which Animate generates and that solves the Google Ads error - but the ad is not displayed correctly then and the create.js file creates other errors now and results in a white ad. I guess I'll need to wait for Adobe to fix it...
For me works:
1) Open libs/1.0.0/createjs.min.js
2) Just delete this part: "canvas_"+
Now h5validator and Adwords successfully passed
nice man, thanks! I've tried something similar by deleting the whole statement there, which then ended in the ad being validated successfully but not displayed properly. Your way works, well done!
SAME! I've just wasted the better part of 2 hrs with this #!%^&#$($($@!!!@) error and your fix just saved my sanity. THANKS!!!
This fix works! - thanks for posting it
brillante habia intentado lo mismo, solo que habia dejado "canvas", y el error seguia llamando a un archivo :lienzo que no existia. en fin esta fue la solucion.
Thank you. Thank you. Thank you! You have no idea how difficult this made my life. Having to have 2 versions of Animate installed just so I can publish with Animate 2019. You deserve a mega high 5!
This solution saved the day! Thanks a lot!
Thanks again for your solution! It's unbelievable that we're already in October 2020, working with Animate 2020, and this is still an issue. I'm working on refreshing banners I created almost a year ago, and I had to go back through my notes to find your solution.
Thank you! Yes, I'm too using this solution for almost a year. Glad I could help
Hello. I'm not totally 100% sure is your problem the same as mine, but here are my research results and how I deal with "Missing Assets Check".
When you publish your work in Animate, both - .HTML and .JS files contain links to your assets (ex .JPG or JS).
If you open your created HTML and JS files in the editor (Brackets for ex) and type CMD+F (find in text) chosse question mark - ? . Usually you will find some "index.js?1578902527610" line instead of having "index.js" or "src:"images/SWB_Logo_250.png?1578902526945"" instead of "src:"images/SWB_Logo_250.png".
This strange things happens when you publish your work from Animate using CTRL/CMD + Enter. It always adds a question mark and some 15 random numbers after each asset.
You have to check both - HTML and JS files.
Another way , more simple, is never publis using Cmd+Enter hotkey, but always use "Publish" button from Publis Settings Panel.
Same problem, very frustrating ...
For now I return to the 2019 release
aqui la solucion
1) Abra libs / 1.0.0 / createjs.min.js
2) Simplemente elimine esta parte: "canvas _"
Disculpa estoy empezando en esto, en que parte encuentro ese lib / 1.0.0 / createjs.min.js
Pues eso cuando la agregar como libreria interna solo copias la dirección web abres en internet luego la guardas como archivo java y le modificas esa parte
This is the solution:
For me works:
1) Open libs/1.0.0/createjs.min.js in Code editor (Dreamweaver works well)
2) Just delete this part: "canvas_"
Use ctrl+f to find the term.
Ironically enough I fixed this by actually using a linked file that GDN allow, i.e. "https://s0.2mdn.net/ads/studio/cached_libs/createjs_2019.11.15_min.js", you can replace the token so it uses the whitelisted remote file, in your HTML template file replace $CREATEJS_LIBRARY_SCRIPTS
Imagine pushing out a new version of Animate, with a version of createjs that is incompatible with GDN, under what circumstances could that possibly happen? If I was super charitable I would say Google updated their validation, but more likely the sad truth is Adobe just didn't even bother to check after making changes if their product still worked for the way 99% customer use it. I understand the actual bug is in the GDN validation and there isn't a missing linked file, but still for this to be pushed to customers is just terrible.