android, google map errors: BaseTileRequest, Server returned: 3

EyeQ Tech picture EyeQ Tech · Sep 16, 2012 · Viewed 9.8k times · Source

I got some strange errors while develop some custom map overlays, anyone experience these? pls help, tks in advance.

BaseTileRequest.readResponseData(BaseTileRequest.java:115)
MapService$MapTileRequest.readResponseData(MapService.java:1473)
MapService$MapTileRequest.readResponseData(MapService.java:1473)

09-17 00:53:25.933: WARN/System.err(32480): java.io.IOException: Server returned: 3
09-17 00:53:25.933: WARN/System.err(32480): at android_maps_conflict_avoidance.com.google.googlenav.map.BaseTileRequest.readResponseData(BaseTileRequest.java:115)
09-17 00:53:25.938: WARN/System.err(32480): at android_maps_conflict_avoidance.com.google.googlenav.map.MapService$MapTileRequest.readResponseData(MapService.java:1473)
09-17 00:53:25.938: WARN/System.err(32480): at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher.processDataRequest(DataRequestDispatcher.java:1117)
09-17 00:53:25.943: WARN/System.err(32480): at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher.serviceRequests(DataRequestDispatcher.java:994)
09-17 00:53:25.943: WARN/System.err(32480): at android_maps_conflict_avoidance.com.google.googlenav.datarequest.DataRequestDispatcher$DispatcherServer.run(DataRequestDispatcher.java:1702)
09-17 00:53:25.948: WARN/System.err(32480): at java.lang.Thread.run(Thread.java:856)

Answer

Leeeeeeelo picture Leeeeeeelo · Sep 16, 2012

I did run into this even though I followed everything said here.

Assuming that you did follow this link, here's how I solved the issue :

Long story :

Everything was working fine until I copied the whole project on another PC and imported it into Eclipse. This changes everything, because the API key you obtain is linked to the debug keystore on the machine that you used to generate the API key. Since I was running / debugging the android application on another machine (hence another debug keystore), the API key was invalid. So I had to generate a new API key as described below.

Short story :

If you are using another machine , generate a new API key, by computing the MD5 fingerprint as described here, and then generate the API key here using this MD5 fingerprint.