Reputation: 19764
I have recently started learning the Google Maps API from here and I did exactly what it was there. I got a key and I used it. But at last the problem was that the map was not displaying!!
I tried all the possible ways to connect the emulator to the internet. My Internet connection has
a proxy server and I tried to specify that from the command line
, from the eclipse itself by going into the run->configurations ... ans so on.
I even changed the proxy settings of the emulator from the settings
option in the emulator. The good news is that the browser
was working nicely, but not my app :(. Even I tried to launch the inbuilt google maps
app in the emulator.
It was showing a message as follows:
There is no working data connection. App exiting.
I don't know why this is happening?. One more thing is that i didn't changed the DNS
settings for the emulator. Will that be a problem? I don't think so because if it were, then browser wouldn't had ran in the first place. I am using Eclipse Indigo
.
Plz help with this weird problem.. Thanx...
Upvotes: 0
Views: 152
Reputation: 722
If the browser works OK, it means that your internet connection is fine. I don't think you need to make specifig config for the network.
My guess is that there is an issue with your api key. You need to create the MD5 signature of your debug certificate, then get the api key associated with it, and use this key in the layout where the mapview is inserted. In the following command line, all that you are supposed to edit is the location of your keystore file :
keytool.exe -list -alias androiddebugkey -keystore "C:\users\ravi.android\debug.keystore" -storepass android -keypass android
Be careful, if you type a wrong password, you will still get MD5 signature, but it will be wrong, and as a result the map would not display.
Upvotes: 1
Reputation: 7615
Perhaps you should try to run the emulator from the console. http://developer.android.com/tools/help/emulator.html
Be sure to pass the following commands: (8.8.8.8 is a DNS from Google)
-http-proxy <proxy>
-dns-server 8.8.8.8
-verbose
If there is any output it might point out the problem further. Possibly the browser has a build in fallback DNS server?
Upvotes: 0