I'm busy with adding a Map View in my android application. I'm trying to get this running on my AVD but I can't get this to work.
I'm following this tutorial: click here. I have to install the Google APIs add-on, so I used the Android SDK Manager to find the add on, but it's not there?
What to do??
Are you including the key in your layout XML (where you have the mapview) that you had to generate from your debug keystore to get the map image to show up? If not, you'll need to do that and you'll need to generate another version to work with your final (non debug) keystore for when you package the .apk.
Here are the instructions from google: http://code.google.com/android/add-ons/google-apis/mapkey.html
Related
My android app is using MapView and hence using the google api's.
Problem is that for testing my app I have to export apk file with my keystore , install the app in device and then run it for checking the output and it consumes a lot of time.
Is there a better way to do it using eclipse??
yes there is.
create a a 'debug maps key' using the debug.keystore located on your user folder, something like:
/Users/<username>/.android/debug.keystore
Follow the lines on this page https://developers.google.com/maps/documentation/android/mapkey#getdebugfingerprint
And register a map key for debug here
https://developers.google.com/android/maps-api-signup
This way, you'll get a debug map key which you can use for your mapview during debug.
I have a little problem. I have created an android api that uses google maps(mapview) on my pc with eclipse and the android emulator. Everything seems to be running fine on my pc, but when I try to install and run the same api on my laptop everything runs great, except that when I navigate to the activity using the mapView, the map shows grey with grids on the screen and not as a map. Could the problem be, that because I am running the api on a different pc, I should create a new api key to use? In another topic, I have seen that a possible solution could be, to change the version of the java compiler to the one that the program was originally compiled. I tried this too to no effect. Any help would be useful.
The Google Maps API key corresponds to your app key, when running the app locally without signing it with a keystore the app is signed by the eclipse debug key (which is different for every computer), so you need to create a new API key for every debug keystore you're using. To sum it up, you need a different API key for each development computer and off-course another API key for your release keystore.
You need to share the debug.keystore between machines for the map to show on different machines while development.
For that in Eclipse, go to Preferences -> Android -> Build and set the Custom debug keystore appropriately which u are using on your pc to view Google Maps.
Or else create a different API key for each development computer.
You will have to create a separate keystore for the release of the app.
For my final year project i am making an android application (Mobile based tracking for personel optimization). Application is heavily dependent on tracking of user for this purpose i need google maps to be appeared on emulator. So, to generate the finger print i need to give the path of file debug.keystore through command prompt but the problem is that i dont know where this file debug.keystore is actually located in my system. I will appreciate your views if you have any idea to overcome this problem.
If you're using Eclipse, you can see this by going to the Window menu and selecting "Preferences" then expand the Android tab and select "Build". There it will show you the path to your debug keystore.
It defaults to
HOME_DIR/.android/debug.keystore
in my app i am trying to show the current location in a map. I followed the instructions in his link
When i run the app from my eclipse to my device by the run config, I am able to view the map and the current place where i am located.
But when i created a .apk and aligned.apk file of my app then i am not able to see the map.
When i was searching through stack overflow i came over the following question
and followed those answers but still i am not able to see the map, it shows only a squares
how to solve this issue
The only reason for this problem is with the keystore which you generate while exporting the apk... Select the already existing keystore androiddebug.keystore available in the android folder... Also remember that you should have valid api key with you..
its better to do in this way
Select the project in workspace-->rightclick---> click export--->export android apps-->next-->next--->enter keystore file name--->next--->enter key alis--->finish
I hope that I can be clear; I know there are a lot of threads on the Google Map API, but I have exhausted my brain trying to fix my problem with the maps. Please tell me what I have wrong here.
I understand there are two Google Map API keys.
1) API key, for a market published app. Maps will appear once the app is published.
2) Debug API key, only works on emulator or side loaded to the phone for testing.
My partner and I are working on an app together from different PC’s. We each have our own debug api key.
1) He sends his app folder from his .android folder
2) I drop the files into folder in my .android folder
3) I import the project into eclipse
4) Replace his API key with mine.
5) Run application
He gets maps displaying on his application, but I do not. I get the gray grid.
Do I need to build a new APK of the app before the maps will appear? Does this new APK have to be created exactly like he did his?
Does the path to my APK need to be in the same folder as my keytool.debug?
How does the fingerprint relate to the APK?
Please clarify, we are stumped.
The maps API key is linked to the keystore which was used to register. You will need the debug.keystore that was used to register for the API key. Here are some quick instructions I found on how to do this.
Sharing one keystore is much easier than changing the reference to a new maps API key every time you make a revision. I'm not sure why your method isn't working though.