The problem with the ability to connect to Google Maps V2

I have received several crash reports and am not sure what causes them.

Only in a recent update did this happen. This may mean that it simply was not before, or I introduced it. The only thing you need to do with the network is to register to get permission to check the network in the Android manifest.

In any case, I hope you can point me in the direction. Here is a crash report.

java.lang.RuntimeException: Error receiving broadcast Intent { act=android.net.conn.CONNECTIVITY_CHANGE flg=0x10000000 (has extras) } in maps.z.bz@405d7d40 at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:722) at android.os.Handler.handleCallback(Handler.java:587) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:123) at android.app.ActivityThread.main(ActivityThread.java:3691) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:507) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:847) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:605) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.IllegalArgumentException: Receiver not registered: maps.z.bz@405d7d40 at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:610) at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:853) at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:331) at maps.z.bz.onReceive(Unknown Source) at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:709) ... 9 more 
+4
source share
1 answer

This happens if you use the Maps V2 api with the old (version 4) and new (3.0.25) version of Google Play services.

It seems that Google has broken backward compatibility, so if people upgrade their Google Play services, the application released with the old library will be broken.

At the moment, you have two options:

  • Release the new version of your application and upgrade it to the new library.
  • Go back to old maps

I raised my ticket and Google has already confirmed this:

http://code.google.com/p/gmaps-api-issues/issues/detail?id=5025&thanks=5025&ts=1362047877

Please run it to get higher priority from Google.

+3
source

All Articles