Skip to content
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

AIR application debug #18

Open
ncannasse opened this issue Jul 5, 2018 · 5 comments
Open

AIR application debug #18

ncannasse opened this issue Jul 5, 2018 · 5 comments

Comments

@ncannasse
Copy link
Member

Is there any way to debug a Haxe/AIR application ? would be a nice to be able to specify a AIR .app XML file instead of the SWF to launch with AIR.

@Gama11
Copy link
Member

Gama11 commented Jul 5, 2018

I'm not very familiar with AIR, does that "just work" with fdb, or does anything additional need to be done to support it? Have you tried simply specifying an .app instead of an .swf? :)

@ncannasse
Copy link
Member Author

AIR applications needs to be launch with adt command instead of the flash player debugger, and it takes a .xml/.app descriptor as parameter that tells about the window size and swf / native extensions to use, that's about it :)

@hansagames
Copy link

hansagames commented Jul 5, 2018

Really to debug air app (apk or ipa) you need to compile it with -connect param (optional IP) then it will wait for fdb to connect and will deliver same data as swf, there is vscode extension for as3 project, as an example. Question is about workflow, as there are 2 ways to achieve debugging, first is to compile app on launch and connect it, and second is to delegate app compilation, wait till its ready and then connect to the debugger. The second approach would delegate compilation to the environment (like openfl or other), as to compile air you need quite a data (icons, splash screens, xml descriptors e.c)

I would go with the simplest way and on debug session just launch fdb and wait till app connects, allowing build, install, launch to be done by specific framework e.c. Similar as remote debugger works in HaxeDeveloper, where you launch it manually and as soon it has connected editor switches in debug mode.

@TomFors
Copy link

TomFors commented Mar 1, 2019

The version of fdb.jar (and related files) that is included in flash-debugger doesn't support AIR applications and won't properly attach. The version of fdb.jar in the AIR SDK and the version included in FlashDevelop both do support AIR applications. Can we get fdb.jar updated to one of these other versions please?

@Gama11
Copy link
Member

Gama11 commented Mar 1, 2019

Pull requests welcome. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants