This is more of an Eclipse error than an Android or Ant error. My Eclipse project won't build because when it sees the build.xml created from the Android command, it starts looking for the debug and release commands. Well, since they are dynamically generated from the <setup> task, they don't exist. So now Eclipse (Build id: 20100218-1602) locking the project from build/run based on these errors. kay.. so here is the weird part: It worked this morning. In fact it has been working for weeks with the build.xml file sitting there. All I did was edit the build.xml file in Eclipse (changed some constants). Ant thinks everything is peachy.
I'm trying to debug native library (in particular, libril.so). Everythig is going fine, breakpoint is being hit, I can go thru the lines of RIL_onRequestComplete() function. But when I tried to print out particular struct I got,
I have mostly been avoiding debugging when I can because of these two problems, so hopefully someone here has suggestions to avoid them:
1. It seems that I have to build the SDK (`make sdk`) and copy it off to a directory for Eclipse to use almost every time I want to debug. I haven't followed through the "sdk" directive, so I'm not clear on why this is necessary instead of just having Eclipse read from the source in my directory. Isn't there some way for it to do this? FYI: I have a (modified) full checkout of Donut, not just the SDK.
2. How can I debug without using Eclipse? I would really like to be able to use something like gdb/jdb.
I installed and eclipse, android sdk and tried the first "hello, android" tutorial but nothing happened on the AVD There are no compilation error, I tried to set break points in the but it does not seem like the application started running at all...
Is this even possible without calling a specific package? I have found countless examples of sending email via intent, but I can find nothing about simply opening the default email client on the device via button press (preferably with a chooser dialog in case the user has multiple clients).
I can no longer run/debug my application in eclipse, when I attempt to I get the following error in the console:Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES.E/PackageParser( 65): Package com.example.foo no certificates at entry assets/community_error.html; ignoring.I have not touched my android config or project configuration, and it was working fine yesterday, i'm running ubuntu/jaunty, i did a kind of security update this morning and i think it might have broken zlib or something.
I am trying to following this documentation 'http://source.android.com/using-eclipse' to debug android Launcher Activity in eclipse.
It said' You may need to open the Debug perspective (next to the "Java" perspective icon in the upper-right, click the small "Open Perspective" icon and select "Debug"). Once you do, you should see a list of threads; if you select one and break it (by clicking the "pause" icon), it should show the stack trace, source file, and line where execution is at. Breakpoints and whatnot should all work.
My question is which threads I need to select in order to debug Launcher Activity? I don't see a thread name Launcher.
I have set up a "Debug Configuration" to debug my Android project. However to get it to debug on a device (HTC Desire) I have to set the Configuration's "Target" to "Manual", there seems to be no way to set in the Debug Configuration that it should go to a selected Device.
It does work, but each debug session I have to "Manually" choose the HTC device from the dialog. Can I set it to always to go the Device?
I'm using Eclipse and have an emulator running Android 2.1 and my IntentService. I'd like to step through my onHandleIntent() overridden function. I've put in a breakpoint on the first statement of the function, which is Context context = getBaseContext();. When the intent is called the program just fails and does not go to debug view in Eclipse.
I am using eclipse android plugins to build a project, But i am getting this error in the console window: [2010-02-03 10:31:14 - androidVNC]Error generating final archive: Debug certificate expired on 1/30/10 2:35 PM!
I uploaded my application to Market and then downloaded it to my phone. Now I'm unable to use debug keystore which is used by default by Eclipse ADT Plugin (Re-installation failed due to different application signatures) and when I'm trying to setup own keystore in Eclipse->Windows->Android->Build->CustomDebugKeystore, I'm unable to enter password or accept keystore and type password later. Is there anything I can do or only way do debug app on device is to uninstall market version and deal with default debug keystore?
I have an application I am writing for Android that basically does a screen scrape of a large table on the web and presents it in a nicer way on the handset. Its 500k of html and takes about 20 seconds or so normally.
When I have my phone hooked up to the computer, I used to be able to just click on "Run" and my code would execute similiarly speedy, as opposed to Debug where it would take 10 minutes to complete.
Now, however, clicking "run" behaves just like debug mode.... I don't want this overhead, how do I get eclipse to stop sending my app to the debugger already? I have searched online and found a couple people with the same issue, but simply rebooting my phone doesn't fix it, and there have been no other solutions posted that I have found.
i install new version of eclipse and Android sdk , but when i run an android project i get this error
Could not open Selected VM debug port (8700). Make sure you do not have another instance of DDMS or of the eclipse plugin running. If it's being used by something else, choose a new port number in the preferences. ADB server didn't ACK * failed to start daemon * i try to solve the problem by following this , but i still get the same problem:
-Window -> Preferences -> Android -> DDMS -Set Base local debugger port to "8601" - Check the box that says "Use ADBHOST" and the value should be "127.0.0.1"
i am also tryng to reinstall android pluing for ecipse and even the android sdk , but i still get the same problem!
The Eclipse build for my 1.6 application project is succeeding and the Ant build is failing. I'm looking for help on why they aren't behaving the same way.
We are developing on Mac OSX 10.5.8 with Eclipse 3.5 against SDK 1.6 + Google APIs. There are no setting changes in Eclipse, either at workspace or project level. Similarly, our ant is also a vanilla-flavored unmodified installation of 1.7.1. JDK is 1.5.0_22. The CLASSPATH environment variable is not set. JAVA_HOME is /Library/Java/Home
The application was initially created by a team member using the Eclipse plugins. The application references two jar files, one of which has a dependency on javax.xml.bind.annotation.XmlSeeAlso, which is not defined anywhere in our code or in android.jar. The other jar file has an explicit dependency on android.jar. I generated the Ant build file using android update.
The Eclipse project builds an apk and runs the application in the emulator. I think this is incorrect behavior.
The Android ant project fails to build. I think this is correct behavior. MyClass.java:98: cannot access javax.xml.bind.annotation.XmlSeeAlso [javac] file javax/xml/bind/annotation/XmlSeeAlso.class not found
Why the two build methods are behaving differently? I would expect them both to fail.
I would like to run a custom shell script upon clicking Build Project in Eclipse. I tried modifying the "compile" section in build.xml, but my script is not getting run. Invoking ant debug on the commandline works, however.
Does anyone know of suggestions/recommendations on how to structure Eclipse projects in order to build an apk from multiple projects? I would like to share classes & resources (strings, layouts, etc.) across multiple apps. How to structure Eclipse projects to do such a thing!
I am using Eclipse 3.5 for Jave EE Developers. Plugins installed include: Android Development Tools, Adobe Flash Builder 4, PDT, PyDev. I have problem with running the application I built. I can start a new project, add a button, and run it on an AVD. Then I add another button, try to run it on AVD, and Eclipse says 1) gen folder is missing, 2) there are errors with build path.
I can get ride of the first error by simply refreshing the project in the left pane, but the second error always sticks around. I searched online and on StackOverflow here and here, although several people have the same problem, there is no definite solution I can find.
I had a project working in Eclipse completely, but after compiling it with ant in order to use Proguard to obfuscate the code the entire project fell apart. The project consists of a single package containing two main activities and 4 helper classes to handle databases and such. After using ant the activities work fine but Eclipse cannot find the helper classes and won't build. Even if I explicitly import the classes the error I get is The import com.ts.routeTracking.DataHelper cannot be resolved while further mentions of the class get the error DataHelper cannot be resolved to a type. How can I get Eclipse and ant to work together?