Note that there are some explanatory texts on larger screens.

plurals
  1. POIssue With Google Maps V2 Connectivity Issues
    primarykey
    data
    text
    <p>I have received a few crash reports and I am unsure what has cause them.</p> <p>It is only in a recent update that this has started happening. This may mean that it just didn't happen before or I introduced it. The only thing to do with the network is register for a permission to check the network in the Android Manifest.</p> <p>Anyway I hope you can point me in the direction. Here is the crash report.</p> <pre><code>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 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload