I know there have been several problems like this, but in all of the threads that I have seen the problem is that the .xml files contain errors(or are named with capital letters or something).
In my case, eclipse won't even generate a R.java when I create a new project that only includes the standard "hello world" example files.
I have restarted, re-installed and recreated projects, but nothing seems to work so in my desperation I am hoping someone has seen a similar problem and knows a solution.
If you run a clean on the project it should regenerate all the generated java files, namely R.
In Eclipse, under the Project menu, is an option build automatically. That would help you build the R.java file every time modifications are made. The Clean... option is also there under Project.
I noticed a very similar problem upon upgrading the version of my Android Development Tools to 22. The solution was to install all updates for ADT by opening...
Help -> Install New Software
... and using the update site...
https://dl-ssl.google.com/android/eclipse/
... to install all outstanding Developer Tools updates.
First of all thanks for answering.
It turned out that after installing the ADT, some SDK packages had not installed, (even though I distinctly remember choosing to install them). I installed those packages and everything seems to be working fine.
Thank you
Related
This is the detailed version of what happened. Please have a little patience and read this. I think my problem is unique.
Initially I had installed Eclipse and followed all procedures and was happily coding my first app. One fine day I fired up the SDK manager and saw the Android Tools had a new update. I tried to install the package. Then may be due to my slow net, something went wrong and Eclipse didn't work at all. It said there was something wrong in some file as an error message.
So I installed Eclipse again and followed all procedures. The address of the workspace and the Android SDK was kept same so that my projects will be automatically imported. But now Eclipse is underlining the R or Resource references in my src files. I do not know what to do.
Did you try opening the sample project that is shipped with andoid SDK? If even that one has the problrm, I think you must update ADT plug-in. Updating SDK and not ADT plug-in caused the problem for me. Once I updated ADT plug-in, everything worked fine.
Having this issue since I upgraded the Android Tools to 21.1. When I start eclipse, even in a clean workspace, I get the error parseSdkContent failed and the details say:
com.android.sdklib.devices.DeviceManager.createInstance
(Ljava/lang/String;Lcom/android/utils/ILogger;)
Lcom/android/sdklib/devices/DeviceManager;
I have searched the internet and tried almost every solution but to no avail. When I go to Android preferences and try to set the path to the SDK , it says no target available. Is there anything else that I can try? I can't do any of my Android Development until it's fixed.
Step 1. Find the folder named: .android
This folder can be located in your Windows user directory, for example in Windows 7 or 8:
C:\Users\YOUR_WINDOWS_USERNAME\.android
Step 2. Delete this folder .android
Step 3. Restart Eclipse and your problem will be solved.
You DON'T have to delete ANYTHING
For me updating the DDMS from ADT plugin did the trick!
Before that, to save time I only updated ADT plugin, nothing else like Android DDMS, TraceView etc., so I ran into same issue.
After a couple of restarts and Google searches everyone was proposing different solutions. I updated my Android DDMS and restarted eclipse and it worked like a charm!
I didn't have to remove my workspace or update my .project file etc.
Ok I just deleted eclipse and reinstalled. Lost all of my settings etc. but it's all I could do. Something must have gotten corrupted in the upgrade of the ADT.
I had the same issue after installing 21.1 on a new machine. Solved it by deleting the default workspace I created during the first launch and then re-starting ADT as Administrator, recreating the workspace. After closing and re-running it as a normal user the problem disappeared.
Re-installing the new version of ADT (which at the time is ADT-23.0.3.zip(http://developer.android.com/sdk/installing/installing-adt.html)) helped me with the same problem you are described above. This message may be a little to late but hope this can also help others.
Uninstalling API 21 and installing API 19 worked for me.
In Eclipse, use the Check For Updates item in the Help menu to update the Eclipse-part of your Android tools (called ADT).
Try to go to your eclipse workspace and delete the .meta folder.
I was recently having the same problem and i figured it out that one must install/update other necessary software related to ADT.Suppose you are updating your ADT then you must also update DDMS with it.So,best option is to install the all software/plugin pack for the version you are updating.
When you uninstall the full thing and install it again,all of these related software get installed in same version so it always solves the problem.
According to me re installing should be final solution.
I got mine fixed by, before restarting your IDE, make your activity main layout as the current tab open, then restart your IDE. Hope it helps :)
This did it for me.
In Eclipse go to
Project Properties -> Java Compiler and set 'Compiler Compliance Level' to 1.7
For me I delete Android 5(API 21) installed software packages from SDK manager.
I am working on API 20 ( Android 4.4w.2). It only solved my problem completely.
Delete .android folder or others didnt help me out.
Deleting ".android" is temporarily fixing the problem with me as after sometime it begins to come again ..
Here is another cause and fix that might help .. This is happening because of existence of 2 versions of SDK in the same machine but in case you have only one version (probably it is 21) just download the SDK platform for API 20 (4.4W) as there is a problem in 21's "layoutlib.jar"). start applying the following:
Close Eclipse
Navigate to your sdk folder (something like C:\adt-bundle-windows-x86_64-20140321\sdk)
Go to platforms folder -> android-21 folder -> data folder and rename layoutlib.jar (for backup only)
Copy the same file (layoutlib.jar) from your android-20 folder to this folder "android-21"
Start Eclipse
maybe you have more than one android IDE installed, for example ,you installed android studio and adt+ eclipse all,just remove one can fix this problem
I was faced with the problem:
error generating final archive debug certificate expired on
but existed ricipes to fix it didn't work. What did I do ?
In C:/Windows/User//.android I deleted the debug.keystore file.
Clean the project
Rerun Eclipse
No results - anyway I see the subject problem.
Trying to fix it, I recreated debug.keystore, using the keytool in my JDK 1.7, copied new file to C:/Windows/User//.android, rerun Eclipse - no results.
Does this problem mean that my problem project and another projects were spoiled by this bug (feature)?
I'm not sure about this particular error, but I've had similar errors that wouldn't seem to go away. If Eclipse really doesn't want to get rid of the error, you may have to reinstall it and start a new project and manually move your old project's java files and resources into it.
Good luck!
EDIT: Also, if you do this, make sure to not use the same workspace folder, as something may be screwed up there to.
OK, I just finished updating Android's SDK+ADT to the latest, and this solved the problem.
Turns out this has nothing to do with Eclipse (so re-installing Eclipse is not really the solution).
The funny thing is... there isn't any debug.keystore in %USERPROFILE%/.android anymore!
(but there is a new file androidwin.cfg in that directory.)
This Android development system is getting weirder by the second... Why install "time bombs" that force me to upgrade for no apparent reason? Let me plan & control when to perform an upgrade. I shouldn't be losing productivity hours in such an unplanned and unexpected manner.
UPDATE: No, updating Android's SDK+ADT to the latest didn't solve the problem. It only deferred it to the stage of running the built application on the test device. This is very frustrating.
UPDATE: Re-installing Eclipse, with a clean install of the latest ADT rev 16, didn't solve the problem either. It seems that the only way out is installing SDK from fresh? It's inconceivable that a fresh Eclipse + fresh ADT + fresh SDK will continue generating this error, so that's the only thing left to try.
UPDATE: Using a completely brand new workspace with the new Eclipse+ADT (but without re-installing a fresh SDK!) did the trick. It seems that the new ADT+SDK combination doesn't like legacy workspaces, or something got corrupted in those workspaces. I need to salvage them somehow because they are critical projects. I'll have to check whether copying the entire workspace to a temporary area, then importing all projects there will do the trick. This is so frustrating.
UPDATE: Success! Using a completely brand new workspace with the new Eclipse+ADT (but without re-installing a fresh SDK!), then importing all my existing projects did the trick. Bounty to be awarded to the one who suggested that. Oh, and the most important thing: Do NOT use this environment on other than the Administrator's account! (the account under which everything was installed).
Delete your debug certificate under ~/.android/debug.keystore on Linux and Mac OS X; the directory is something like %USERPROFILE%/.androidon Windows.
The Eclipse plugin should then generate a new certificate when you next try to build a debug package. You may need to clean and then build to generate the certificate.
After steps 1-3 just delete this error from problems (select it in "Problems" view and click "delete"). After this everything will be fine.
I had a working Eclipse setup with 3.6.2 and SDK tools from version 11, and it has been building my main project just fine for quite a while.
For a different project, I thought I needed to upgrade my SDK to the latest and greatest - at this point API 14 (ICS 4.0).
I cannot even reconstruct the steps I went through, but what happened was that my project would seem to build, but I would see that it would say that it was skipping a post-compiler step, and at the end I would have no APK.
I also noticed that it updated my .classpath so that the output path was bin/classes instead of .bin.
Along the way I tried updating my Eclipse to the latest version (Indigo 3.7.1) but this didn't help.
I solved the problem eventually with help from this post on the Google Android forum:
http://code.google.com/p/android/issues/detail?id=21031
For me personally the biggest issue seemed to be solved as follows (qutoe from comment 25 in the forum post)
"I seem to solve the problem with .apk files not being built automatically until run/debug is used (comments #10, #11 etc.). Go to Windows -> Preferences -> Android -> Build and uncheck "Skip packaging and dexing until export or launch" then restart Eclipse. Works for me."
But there is other useful material there. Different people with different projects seem to have different problems with this setup.
I still don't understand the change in the classpath, but it doesn't seem to matter.
In addition, I found a discussion of installing the ADT with Eclipse Indigo which was helpful here in Stackoverflow:
Eclipse Indigo - Cannot install Android ADT Plugin
I also found that I guess because of various uninstalls/reinstalls, for some reason it stopped excluding my .svn directories from the sources. This Stackoverflow post was helpful with that:
Why is eclipse trying to copy my .svn folders from src to bin, and how can I make it stop?
Finally: a tip for really and truly uninstalling Eclipse - everybody says there is no uninstall, and there isn't, but there is a directory that Eclipse leaves in your home directory (in windows 7 under c:\users\) called .eclipse -
Zap it if you really want to start fresh.
In addition, for less extreme measures, there is Project->Clean inside Eclipse, and you can invoke eclipse with "eclipse -clean" for additional cleansing effects. No idea what, but various helpful people along the way suggested trying that to solve problems.
Ah yes - when I first installed Indigo and tried to build, I got a warning that my Java Compiler Compliance level was not up to snuff, which was simply not true - I have only Java 1.6 installed on my machine.
See this post for somebody who had similar experience:
http://marakana.com/forums/android/general/374.html
For me, what worked was simply going to Project, Properties, Java Compiler, then click on Configure Workspace Settings, and click on Ok in the dialog. Didn't need to actually change anything. Just showed it that everything was ok!
Eventually I indeed did clean out my Eclipse and Android installations (including the aforementioned .eclipse directory, and there's also an .android directory in your home directory which you may want to erase if uninstalling the Android SDK Tools doesn't do that - this actually is uninstallable). Installed everything from scratch and then used the additional information provided above and now it's building my APK.
I hope this saves somebody the hours I spent getting my build back in shape.
After several years with Eclipse and Android development this combination is driving me nuts.
On every start of Eclipse the lib settings I've configured on the page 'Project/Properties/Android' section 'Lib' need to be re-applied.
After a Eclipse restart all existing projects are marked in red. For every project I have to select that project, change to the page described above, remove all Libs, hit Apply, re-enter the same Libs and hit apply again. .classpath and .project look ok. It's the latest Android SDK and the latest Helios Eclipse release. MotoDEV is installed as plugin.
This is a stupid and time-consuming process. Please, has anybody an idea what's wrong with Eclipse (or the Android SDK) or my configuration?
Many thanks in advance.
Which OS are you using and is it 32- or 64-bit? Are you logged in as root/administrator or as a regular user? This sounds suspiciously like the ~/.eclipse folder isn't getting written correctly. We can look at this in MOTODEV Studio and see if it's something unique to us, but it definitely is strange behavior.
Update: one of the MOTODEV Studio team says this is a known bug in ADT when using linked folders. http://code.google.com/p/android/issues/detail?id=14217