Skip to main content
Participating Frequently
June 2, 2022
Question

Both testing and publishing animation won't work

  • June 2, 2022
  • 1 reply
  • 1689 views

I am extremely new to Animate and have made one animation that worked fine before this. When I test my animation inside of Animate it brings up my browser but shows a blank screen. When I try to publish the animation and play that, it does open, but it stays stuck on the first frame and the button doesn't work.

 

When I test in Animate the console says:

 

"Uncaught (in promise) DOMException: The buffer passed to decodeAudioData contains invalid content which cannot be decoded successfully."

 

I checked the console when I open the published file and it gives me:

 

"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at (insert my file name here) AudioPluginTest.fail. (Reason: CORS request not http)."

and

"Uncaught An error has occurred. This is most likely due to security restrictions on reading canvas pixel data with local or cross-domain images."

This topic has been closed for replies.

1 reply

kglad
Community Expert
Community Expert
June 3, 2022

is this canvas or as3 document?

 

and, if canvas, what does the developer console say when you use animate to test (control>test movie>in browser).  this is going to be very different from opening the published html file with your browser and then checking the console (which you expect to give the message your reported).

Participating Frequently
June 3, 2022

It's a canvas document. Animate gives me "Frame numbers in EaselJS start at 0 instead of 1. For example, this affects gotoAndStop and gotoAndPlay calls. (5)" and
"Content with both Bitmaps and Buttons may generate local security errors in some browsers if run from the local file system."

 

I asked for help from my professor and she says the project works perfectly fine both testing and publishing wise, so I don't understand why it doesn't work for me?

Colin Holgate
Inspiring
June 3, 2022

There are publish settings that control whether the images are saved seperately as individual files, or combined into a sprite sheet or texture map. Either of those two settings have tougher security options. It could be that you're testing and using a sprite sheet, and your professor is testing with individual image files.