mapbox-java: Look into reason why LOST can't handle multiple processes in an application.

When location permission enabled and you’ve included a process in your activity inside the manifest, the application will crash with the following error:

03-20 18:04:14.191 5568-5568/? D/sysproxy: [D:5111] Look up api.mapbox.com.
03-20 18:04:14.191 5568-5568/? D/sysproxy: [D:1cd2] Look up events.mapbox.com.
03-20 18:04:14.247 7383-7383/com.mapbox.mapboxandroiddemo:test D/AndroidRuntime: Shutting down VM
03-20 18:04:14.257 7383-7383/com.mapbox.mapboxandroiddemo:test E/AndroidRuntime: FATAL EXCEPTION: main
                                                                                 Process: com.mapbox.mapboxandroiddemo:test, PID: 7383
                                                                                 java.lang.ClassCastException: android.os.BinderProxy cannot be cast to com.mapzen.android.lost.internal.FusedLocationProviderService$FusedLocationProviderBinder
                                                                                     at com.mapzen.android.lost.internal.FusedLocationProviderApiImpl.onServiceConnected(FusedLocationProviderApiImpl.java:45)
                                                                                     at com.mapzen.android.lost.internal.FusedLocationServiceConnectionManager.onServiceConnected(FusedLocationServiceConnectionManager.java:79)
                                                                                     at com.mapzen.android.lost.internal.FusedLocationProviderApiImpl.onServiceConnected(FusedLocationProviderApiImpl.java:65)
                                                                                     at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1453)
                                                                                     at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1481)
                                                                                     at android.os.Handler.handleCallback(Handler.java:751)
                                                                                     at android.os.Handler.dispatchMessage(Handler.java:95)
                                                                                     at android.os.Looper.loop(Looper.java:154)
                                                                                     at android.app.ActivityThread.main(ActivityThread.java:6119)
                                                                                     at java.lang.reflect.Method.invoke(Native Method)
                                                                                     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
                                                                                     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
03-20 18:04:14.270 1443-1608/system_process W/ActivityManager:   Force finishing activity com.mapbox.mapboxandroiddemo/com.mapbox.mapboxandroidweardemo.examples.SimpleMapViewActivity
03-20 18:04:14.276 1443-1608/system_process W/ActivityManager:   Force finishing activity com.mapbox.mapboxandroiddemo/com.mapbox.mapboxandroidweardemo.MainActivity

cc: @zugaldia @Guardiola31337

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 23 (8 by maintainers)

Most upvoted comments

Just a heads up- we are targeting a 2.3.0 release in the next few days and would love feedback. Please report any issues you have had integrating the 2.3.0-SNAPSHOT. Thanks for your patience and help, we’re looking forward to getting a new stable version out!

sarahlensing on May 11, 2017

This has now been fixed upstream, I’m adding this ticket to the next milestone as a release blocker hoping that we can include the fix (we’re depending on LOST releasing 2.3 on time).

zugaldia on May 2, 2017

Thank you to everyone who makes these projects possible ❤️

dazza5000 on Apr 7, 2017

The work isn’t complete in the upstream ticket yet. https://github.com/mapzen/lost/issues/173#issuecomment-294585570

We’re getting there though 😃

msmollin on Apr 20, 2017

@msmollin Please see https://github.com/mapzen/lost/issues/173#issuecomment-290208018 for details. Bottom line is that we still see the issue after upgrading to LOST 2.2.0.

zugaldia on Mar 29, 2017