I just changed the icon for the app and now I'm getting the dreaded AndroidManifest.xml file missing after re-downloading the source code. Shit! I know I have everything installed right. It was working fine 15 minutes ago. Bruce

Can't even load the old project back into Eclipse. Same error message. Bruce

I GOT THAT 2

How did you fix it?

i havnt yet

This totally sucks. I can not find one post anywhere that helps with this problem. I looked everywhere online and can't seem to find a damn thing that works. No one on buzztouch had this same problem when re-compiling? b

I notice a few things in Eclipse. There's a little red x next to the src folder. Inside the src folder is another folder with a little red x called com.v1_4.B5F64A6950B99593.com Inside that folder are a bunch of icons with red icons and ! icons next to them. Does this mean the java files are somehow disconnected? From what I have no idea? Bruce

Hi guys; This is strange behavior and for sure easily fixed. Just gotta figure out why Eclipse is yelling at us. The little red arrows are exactly waht trailman thought, a way for Eclipse so say ' hey somthings wrong with this file' So all you did was change the icon (presumably on the control panel) then re-downloaded - something's not adding up. The AndroidManifest.xml file tells Eclipse (and the phone) how the source code is arranged, what the package name is (a fancy name for the folder that contains all the source code and assets) and other good stuff. This means that com.v1_4.B5F64A6950B99593.com should be at the top of nearly every file. 'Hey Eclipse, all the source code in my project is part of this package' Is the AndroidManifest.xml file actually missing? You should be able to easily see it and open it in Eclipse with the project open. If you can, see if it has a package name that matches com.v1_4.B5F64A6950B99593.com - it needs to and should. The part that baffles me is what happened between the when Eclipse had 'no problem with it' and changing an icon on the control panel. Could it be some sort of conflict in the place where you downloaded the folder to? Like maybe there are two projects in that directory (the old one and the new one you downloaded) and Ecplise doesn't know which one to use? Grasping here, makes no sense. WE MUST FIGURE OUT A WAY TO HELP FOLKS DO THIS WITHOUT THESE KINDS OF STRESSORS. It's CRAP that this isn't easy like it is in iOS. I think I found my weekend video / tutorial / explanation to create. Just can't find a way to make it smooth as it should be - pout face.

Thanks for your reply, it's moments like these when I can't do it myself that are the scariest part of the process. I am always worried about stuff like this when I try anything new. It's always what I don't know that bites me in the ass. I followed the instructions I read in a few posts before changing the icon and re-downloading the source code. I thought ok this shouldn't be too much of a hassle but once again I got bit. I realize this has nothing to do with buzztouch so don't think I'm casting any aspersion there. It appears to me that Eclipse is where the bugs are (or where my lack of knowledge is) and we should all realize we're swimming in the deep end even if we don't know it when we attempt to compile or do certain things (like get the MD5 Fingerprint :-) ) that does take some skill and attention to detail to figure out. There's no way around that, that I can see. The AndroidManifest.xml is not missing it's right there in Eclipse. I can click on it and make changes. It appears that all the problems are in the java folder com.v1_4.B5F64A6950B99593.com. All map stuff. I've got Errors 100 of 101 items. I've got Warnings for 100 of 167 items. I have only 1 Android buzztouch folder with the source code in it (in my Documents folder,always has been) and I emptied the trash. What's weird is the simulator still works but without the new icon. Is that a clue? As an aside, when you say you can't get the video to be smooth what do you mean? My trade is video production. I may be able to help you with that one. Bruce

Thanks for your reply, it's moments like these when I can't do it myself that are the scariest part of the process. I am always worried about stuff like this when I try anything new. It's always what I don't know that bites me in the ass. I followed the instructions I read in a few posts before changing the icon and re-downloading the source code. I thought ok this shouldn't be too much of a hassle but once again I got bit. I realize this has nothing to do with buzztouch so don't think I'm casting any aspersion there. It appears to me that Eclipse is where the bugs are (or where my lack of knowledge is) and we should all realize we're swimming in the deep end even if we don't know it when we attempt to compile or do certain things (like get the MD5 Fingerprint :-) ) that does take some skill and attention to detail to figure out. There's no way around that, that I can see. The AndroidManifest.xml is not missing it's right there in Eclipse. I can click on it and make changes. It appears that all the problems are in the java folder com.v1_4.B5F64A6950B99593.com. All map stuff. I've got Errors 100 of 101 items. I've got Warnings for 100 of 167 items. I have only 1 Android buzztouch folder with the source code in it (in my Documents folder,always has been) and I emptied the trash. What's weird is the simulator still works but without the new icon. Is that a clue? As an aside, when you say you can't get the video to be smooth what do you mean? My trade is video production. I may be able to help you with that one. Bruce

The 'smooth' remark was related to the idea that we can't find a way to make the Android Compile process smooth, not a video - funny. But, thanks for the help, may just hit you up on that again. Map errors are always related to Eclipse not having the Google Maps API's installed. You've been down this road before though. I'm thinking this may be easier. a) Delete the app from Eclipse. (Say yes if it asks you if you want to delete the source-code too) We want it totally gone - 100% b) Re-download your project from the control panel. c) Eclipse > New Project > Android Project > From Existing source just like it was the first time you did it. Can't think of anything else.

If I choose Google API's (1.6) instead of Google 1.6 it works but it still has the old icon in the simulator? Bruce

I'm sorry, if I choose Android 1.6 for the Build target it doesn't work. If I choose Google API's it works with the old logo. Bruce

I'm deleting everything off my computer and reloading Eclipse and the sdk...

No go: [2011-02-26 14:40:05 - com.android.ide.eclipse.adt.internal.project.AndroidManifestHelper] Unable to read /AndroidManifest.xml: java.io.FileNotFoundException: /AndroidManifest.xml (No such file or directory) What do I do now? I'm at a dead end Bruce

I don't think the above error message is reliable. That is not where I told Eclipse where the buzztouch folder is. I now am getting a completely different error message without changing anything. Clueless

So... if you can get Eclipse running on your machine, figure out how to remove apps from the simulator. Do this just like the real device. from the home screen tap menu > settings > applications > the app you want to remove > remove Builds: You'll want to use Google 1.6 API's (slightly different than Android 1.6 API's). It does sound like you've got a screwy configurtation going on. I really REALLY wish I could reach-through the screen and see / fix what's happening. Not sure how. Oh, wait.. .maybe we could do a weekly webinar or something with some screen sharing so we can help? Hmm.. we get Anroid / Eclipse questions constantly - this may be a good approach?

Finally got it going! After a clean install of eclipse and SDK. Eclipse is just so funky. I don't know what happened but something got corrupted I guess. The one good thing about all this bs is that we get a little more comfortable with being in these environments. So the last thing is that my app won't load in the simulator: [2011-02-27 19:08:11 - Sedona Vortex] Android Launch! [2011-02-27 19:08:11 - Sedona Vortex] adb is running normally. [2011-02-27 19:08:11 - Sedona Vortex] Performing com.v1_4.B5F64A6950B99593.com.Act_Home activity launch [2011-02-27 19:08:11 - Sedona Vortex] Failed to find an AVD compatible with target 'Google APIs'. [2011-02-27 19:13:50 - SDK Manager] Created AVD 'PhoneAndroid2' based on Android 1.6, [2011-02-27 19:13:50 - SDK Manager] with the following hardware config: [2011-02-27 19:13:50 - SDK Manager] hw.lcd.density=240 [2011-02-27 19:13:50 - SDK Manager] vm.heapSize=24 [2011-02-27 19:41:14 - SDK Manager] Created AVD 'androidphone3' based on Android 2.2, [2011-02-27 19:41:14 - SDK Manager] with the following hardware config: [2011-02-27 19:41:14 - SDK Manager] hw.lcd.density=240 [2011-02-27 19:41:14 - SDK Manager] vm.heapSize=24 What am I doing wrong now? Bruce I know I had a nice link last time, explaining how to setup the AVD. But since I have so many browsers and so many bookmarks I can't remember where the heck it is. ;-)

As far as I can tell I've downloaded all the API's... b [2011-02-27 20:15:38 - Sedona Vortex] Still no compatible AVDs with target 'Google APIs': Aborting launch. [2011-02-27 20:15:38 - Sedona Vortex] Still no compatible AVDs with target 'Google APIs': Aborting launch. [2011-02-27 20:15:38 - Sedona Vortex] Performing com.v1_4.B5F64A6950B99593.com.Act_Home activity launch [2011-02-27 20:15:38 - Sedona Vortex] Performing com.v1_4.B5F64A6950B99593.com.Act_Home activity launch [2011-02-27 20:15:42 - Sedona Vortex] Launch canceled! [2011-02-27 20:15:44 - Sedona Vortex] Launch canceled!

AWESOME. Youre soooo close. This sounds like Eclispe is doing everythign we want. There is another level of complexity to understand. With Apple and iOS, working with a simulator is easy because they control the simulators. All of us run the exact same simluator so it always works. In Android, it's a bit different because there are SO MANY different devices. The idea is that you can 'build' your project to target a certain device. In our case, we've built the project with 'any device running Android 1.6 or higher' So, all we need to do now is setup a simulator (Android calls it an Emulator, or a Virtual Device) that is running the right system. The reason we have to do this is because you could in theory setup dozens of different simulators running all different version of Android. We want to to a 1.6 simultor. You do this by adding simulators to the Virtual Device list. This means you need to find the virutal device list, then create a Virtual Device with the Google 1.6 setting checked. I'm hoping this makes sense. Next, when you click 'Run' - you'll want to make sure Eclipse is launching the right simulator. The best way to ensure this is to only have one simulator in the AVD list. Rooting for you in Monterey.

As far as I can tell I've downloaded all the API's... b [2011-02-27 20:15:38 - Sedona Vortex] Still no compatible AVDs with target 'Google APIs': Aborting launch. [2011-02-27 20:15:38 - Sedona Vortex] Still no compatible AVDs with target 'Google APIs': Aborting launch. [2011-02-27 20:15:38 - Sedona Vortex] Performing com.v1_4.B5F64A6950B99593.com.Act_Home activity launch [2011-02-27 20:15:38 - Sedona Vortex] Performing com.v1_4.B5F64A6950B99593.com.Act_Home activity launch [2011-02-27 20:15:42 - Sedona Vortex] Launch canceled! [2011-02-27 20:15:44 - Sedona Vortex] Launch canceled!

So, New Android project, choose Google API's 1.6 then which AVD? Google API's? or Android 1.6 or higher? Bruce

Got everything working again! Thanks for your time David. Also, I changed the icon again just to see if I was going crazy. (I know, you think I'm crazy for tempting fate once again... ) This time I deleted the old files from Eclipse, Quit, Deleted the old Buzztouch folder from my documents folder, then copied the new buzztouch folder back to where the old on was, created a new Android Project in Eclipse, ran it and I got the same error message AndroidManifest.xml missing. I quit and re-launched Eclipse and everything was ok. So basically Eclipse is f&%$cked and finicky. Which brings me back to a basic troubleshooting lesson. ALWAYS quit first, relaunch. If that doesn't work restart the computer. If that doesn't work then hit the web for answers. Since I broke my own rules i got into trouble. I can see why Apple has the closed system. It's a smart business model in one way because they don't have as many hardware issues. Which lead to software issues which leads to support issues. We'll see how long the system can be sustained for. b

The Google ApI's 2.3.1 API Level 9 worked. Got everything working again! Thanks for your time David. Also, I changed the icon again just to see if I was going crazy. (I know, you think I'm crazy for tempting fate once again... ) This time I deleted the old files from Eclipse, Quit, Deleted the old Buzztouch folder from my documents folder, then copied the new buzztouch folder back to where the old on was, created a new Android Project in Eclipse, ran it and I got the same error message AndroidManifest.xml missing. I quit and re-launched Eclipse and everything was ok. So basically Eclipse is f&%$cked and finicky. Which brings me back to a basic troubleshooting lesson. ALWAYS quit first, relaunch. If that doesn't work restart the computer. If that doesn't work then hit the web for answers. Since I broke my own rules i got into trouble. I can see why Apple has the closed system. It's a smart business model in one way because they don't have as many hardware issues. Which lead to software issues which leads to support issues. We'll see how long the system can be sustained for. b

Great news! Yes, if we had our way, we'd single-handedly figure out a way to eliminate all the $$**#&$$ associated with Eclipse! But, another way to look at it is this... if we can find a way to streamline this process then we'll be helping too ;-) Glad to help.