Hi there; When i try to run the app from eclipse in the emulator, the emulator loads but can't see the icon anywhere [it should be inside the apps like the 1.4] Any ideas? Thanks M

I'm running into the same problem...keeps saying i don't have the correct API selected...I built both a tablet and 2.1/2.2 emulator...

Make sure you use the correct Google API as specified in v1.4 and v1.5 release notes. They are different for each, and this is very likely your issue.

And make very sure you are using the Google APIs, and NOT the Android APIs...the Readme is very specific about that!

You'll also need to create a virtual device that works with the new Google API version. You want to open the Android SDK and AVD Manager and select 'New' to create the device. Devices created for previous versions of the API won't work.

Excellent point, @MGoBlue! And while we're at it, don't forget to create your debugkeystore and releasekeystore!

Hey guys, very much a newb here...working with someone who knows JAVA but not android so we are trying to teach ourselves. When I create the virtual device, what api should i select? I selected 2.1, 2.2, and 3.2 yet I still can't get it to run...what am i doing wrong?

Sorry for the dumb questions guys, very much a noob here. I created an emulator with google api's 2.1, 2.2, and 3.2, yet i still can't get the emulator to run...what am i doing wrong? What api should I run, and how should i set it up? thanks in advance!

If you're using the correct API, which it sounds like you are, then you need to make sure you create a virtual device. The video that they have here - http://www.buzztouch.com/account/ - regarding Android compiling, will show you how to do this.

Thanks @GoNorthWest, will check out those videos...though i was able to get the 1.4 to run fine...

Same deal on creating the virtual device, then. Just base it on the new API (Google API's Platform 2.2 and API level 8) instead of the old one (Google API's Platform 1.6 and API level 4) and you should be good!

this is what comes up when i try and load it (I created a tablet emulator and tried to run it on that...) [2011-09-16 16:04:19 - MM2000V2] HOME is up on device 'emulator-5554' [2011-09-16 16:04:19 - MM2000V2] Uploading MM2000V2.apk onto device 'emulator-5554' [2011-09-16 16:04:25 - MM2000V2] Installing MM2000V2.apk... [2011-09-16 16:06:43 - MM2000V2] Failed to install MM2000V2.apk on device 'emulator-5554! [2011-09-16 16:06:43 - MM2000V2] (null) [2011-09-16 16:06:44 - MM2000V2] Launch canceled! I have no idea why it keeps failing to install the app...

Do you have the debugkeystore configured correctly? Did you make that change in strings.xml?

Unfortunatly both those things are a little over my head...i will do some research into them i suppose...

In order to publish or test your apps, you need a key to sign the apps. The official information from the SDK can be found here : http://developer.android.com/guide/publishing/app-signing.html Without a signature, they simply won't install. You can have a release certificate, and a debug certificate. A good, quick tutorial on how to get those keys can be found her : http://chuckbeasley.com/index.php/2011/06/26/getting-your-google-maps-api-key-for-android/ I know that talks about map API keys, but it will generate the appropriate keystore stuff, which you then need to generate the apk. Hope this helps a bit. Tripped me up for a few hours! Mark

Ok, the virtual device I created is using the newest api, 2.2 level, now i can see the app icon on the apps section, but when I click on the icon, the app crashes: The application Cars (process com.cars) has stopped unexpectedy. Please try again I am sure this could be related to many things, including the facebook api, I will need to investigate. Now I have a question for Mark: do you need to have the debugkeystore and releasekeystore configured propperly to test the app in the emulator? Thanks guys M.

It could be an issue with screens that aren't supported yet. Check the readme to check what is and is not working in this version.

To be honest, I'm not sure if you need the keystore in order to test in the simulator. But, I figure better safe than sorry, and one less thing I have to worry about when I'm ready to release. If you can get some info from LogCat, we may be able to help you out more : 4) Console Output (LogCat): Get good at running the console in Eclipse so you can see what's happening while your app runs. We went through great pains to write literally thousands of lines of code meant only for the developer - you. When you find something you think we can learn from, paste a small snippet of your consoles output on the forum. Pasting a GIANT console output is bad and almost useless. Clear the console, tap a button or screen, paste that small amount of output that displayed for that single action. It's a bit tricky to display the Console. Called the LogCat in Android world. Choose Window > Show View > Other > Android > LogCat. When viewing the output, use the W button to show only the buzztouch output. All the output created by your app begins with ZZ and each line of output will tell you the class file and the method. IMPORTANT: If you're running on a device the LogCat process does consume memory and may affect the performance of your app. You can turn off debugging by setting showDebugOutput to false in your app's delegate.java file.

Thanks guys.

thank you mgoblue!