Just to make sure my week goes as smoothly as possible I installed ADT 14 / SDK 14 for the new Android 4.0 build and now I can't build anything on my Win7 64bit box.
First I installed the new SDK. Then I installed the new ADT after I got some errors. Now I just get an error that my project has errors but not a single window will tell me what the error happens to be. I installed the SDK from scratch and still have the same error. I installed a fresh version of Eclipse 3.7, ADT 14 and SVN plug-ins and still have the same issue. I have run every update possible. Our bandwidth sucks right now so this is taking a really long time and I am getting really tired of experimenting. I will have to give this a try at home to see what happens there tonight.
I did cleans before I did builds and did the Android -> Fix Project menu item but nothing will get me past the error message that I have a project error but nothing will tell me what the error is. Not a single file, other than the main project, is marked as in error. I see others are having the same issue on the web. I looked in the project properties and nothing is showing up as in error there either.
At this point I am running Eclipse on my Mac as it has not been updated to 14. No idea what to do next. I just got out of the iTunes / Xcode / iOS 5.0 install hell. At least that is all working. Now I get to be really annoyed at Google / Android from screwing this up. Guess I can blow away all the version 14 stuff and go back to 13 to see what happens. Seems this is all a bit rushed.
Well not the fault of Eclipse or Google on this one. My developer certificate happened to expire at the exact same time I installed the update. Once I deleted the old certificate off my HD an let Eclipse build a new one all was fine. Somewhere in there showing errors in the Problem tab had gotten turned off - it was only showing warnings thus it looked like nothing was wrong. What a huge waste of time and energy it took to figure all of this out. I wish the error message would show your the current error list instead of just saying "there is an error, good luck finding it!"
facing the same issue! damn.
ReplyDeleteI feel your pain. Hopefully you get around it. Seems a lot of folks had issues with ADK 14. At least is is now running fine for me.
ReplyDeleteI did have to re-associate XML files to the Android GUI editor otherwise I could not see any of my layout *.XML files in the graphics editor. While I don't edit them in there, I manually edit the XML, I do use it to verify my layouts look they way I think they should before I run it on the device.