Skip to content
This repository has been archived by the owner. It is now read-only.

debug mobile device #11

Open
lrkwz opened this issue Jun 25, 2013 · 3 comments
Open

debug mobile device #11

lrkwz opened this issue Jun 25, 2013 · 3 comments

Comments

@lrkwz
Copy link
Contributor

lrkwz commented Jun 25, 2013

I guess that in order to debug the app deployed on mobile device you should add the -connect parameter. I think that <target>apk-debug</target> is not enough.

@fomkin
Copy link
Owner

fomkin commented Jun 25, 2013

Actually I don't think that this plugin is a tool suitable to preparing debug packages. This is job of IDE. I will approve patch if you make it.

@lrkwz
Copy link
Contributor Author

lrkwz commented Jun 27, 2013

Well I think that you can safely develop using maven as a build environment and the sdk tools for debugging whatever IDE you decide to use (vi, emacs, gedit, notepad are perfect candidates don't you think so?).
I'll prepare a path as soon I can find some spare time :-)

@Antoine-Lassauzay
Copy link
Contributor

You are right about the -connect parameter. This will make the AIR runtime listen for debugger connections from the Flash debugger (fdb). However, I noticed that most IDEs (IntelliJ and most likely Flash Builder) won't let you start debugging sessions without repackaging/re-installing the game on device. Using fdb from the command line, you should be able to launch debugging sessions "the hard way" :)

If you wish to debug native/Java code used a Native Extension from your app, I don't think the -connect parameter is need though. (see http://diadraw.com/how-to-debug-your-android-ane/)

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

No branches or pull requests

3 participants