I created a Desktop AIR in Adobe Animate CC 2017 with AIR 23, when Test everything works, after Build in my pc everything works, when test to VirtualBox (Application with runtime embedded) it run but some features like buttons events and url events doesn't works, what is problem?
After review codes and test for many times i found correct issue, when a hidden runtime error occurred some related part doesn't works properly, I used try() catch() for handle errors and external video playback instead embedded, now build works on other computers without problem.
Related
Adobe Animate cc 2017 - HTML5 freezes when I publish/test project with audio
I'm working on a small game, using Animate 2017 and exporting it to HTML5. I'm using createjs.Sound to add the sound fx I've added to the library. When I publish or "test" the project, it freezes the loading bar. On OSx it stays at 0%, on windows it goes up to 70% but freezes anyway. The only option being to force quit the app. I'm following a tutorial from Pluralsight, and I've tested the tutor's project and I get a slightly different issue, the project gets published, the browser starts everything automatically but nothing happens afterwards, instead of the game starting, it just stays a black canvas (no errors in the console).
A few more data to help troubleshoot, the tutor's project is using .mp3 files and I'm using .wav audio. I've been trying to look through the OSX auto generated error report, but I can't make heads or tails of what it says.
Animate mac/windows version - 2017.0.1 Release (16.0.1.119)
Turns out it was a corrupted symbol or something that was causing the program to crash. Converting the project to ActionScript 3 and then back to HTML5 solved the issue.
https://forums.adobe.com/thread/2425008
If anyone experience a AnimateCC crash issue in Mac, It might be an issue with long audio file name. I found that if the audio file name is greater than 29 characters, AnimateCC crashes when publishing. Here is a sample test file.
https://drive.google.com/file/d/1dEBdM4laszCXFa3Bz4tS3yHh-8PbLaGo/view?usp=sharing
As you can see, the file crashes when you try to export. It has only one sound file in the library. When you remove one character in the file name, it gets published successfully. I tested this in AnimateCC version 18.0.2 (Build 126).
I have selenium tests running against chrome driver v 2.25. I have chrome v 54 installed on a ubuntu 14 server. I cannot get selenium tests to play video player that is in flash. Is there a plugin I need to install to get chrome on ubuntu to support flash?
The test loads a page with a video player and checks that there is a play button. I need to make sure that the server can load flash.
Selenium cannot and will not automate embedded objects in any website.
This includes objects such as:
Flash
PDF
Java Applets
etc.
If you want to automate those, you will need to find a different tool. Selenium is designed to automate websites, not external components of a website like flash.
Got this working wit chrome 52+ and chromedriver 2.22+
At time of answer it works with chrome 55/2.27 - both 64 bit
all you need is add extra flag to chromedriver
--ppapi-flash-path=chromedriver/chromedriver_linux64/libpepflashplayer.so
I'm quite new to AS3 and now I need to solve a swf crash problem.
I have the source code and fla file, so I can debug/run it in FL, I can use trace to print out log. The problem is, on my machine, either run in FL or generated swf embed in IE works correctly. But the swf always crashes on tester's machine.
Because the swf is run in IE, trace seems doesn't work, so I'd like to know if there's any tool I can use so that I can see all the trace output on tester's machine.
Thanks
Trace only works while working directly with Adobe Flash.
What you can do is call a javascript alert to display the Trace elements inside a BROWSER. Please note it will not work while directly opening the .swf
ExternalInterface.call("alert",output);
But their should be no different in handling any .swf except for the installed Version of the Flashplayer on each computer.
If it runs fine on your IE, then it should on the other as long as Flash Version and IE Version are the same.
Outdate Version usually lead to this sort of conflict.
I create app using flash cs 5.5. It works fine. Then I started using flash cs6. The app was running fine until today. It runs fine but the problem is when i tried to publish it, it start playing but after some time(about 30 secs), swf file terminates itself. There is no problem in using cs5.5. It's just when i tried to publish it, it runs and swf file is close itself. Do any one have any idea what might be the problem ?
When you say "the swf file terminates itself", are you talking about the standalone flash player? Normally if this happens, it's because an error was thrown, but if you're not using the debug player, you won't see it, it'll just close.
Download the debugger player here: http://www.adobe.com/support/flashplayer/downloads.html and run your swf in debug mode (so all the debug symbols are present and you get the most complete error message). This should give you an idea of what the error is, and where to go to fix it.
NOTE: to know if you're running in the debug player or not, right-click on the swf in the player, and if you see an option for "Show redraw regions", then it's the debug player
Flash app I've built works fine on desktop and on IIS6, but when I upload to IIS7+ it breaks.
Most of the app appears to work as expected but a crucial test fails. I think it's a custom event that is failing, but I've no idea why when it works perfectly everywhere else.
Anybody else has issues with Flash and IIS7+?
My app is built with Flash CS5 and AS3 for Flash player 10.
BTW it's not a MIME type issue.
Any help appreciated.
Thanks
Barry
Don't use the '+' character in filenames on servers running IIS7+. IIS7 treats these as if they were query strings. So a filename 'hello+world+today.jpg' will be translated into 'hello.jpg?key=world+today'. This sometimes fails silently in Flash without throwing an IOError, assuming you set up to receive one of course.