Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Update to stable version of LOST #8939

Closed
zugaldia opened this issue May 9, 2017 · 11 comments
Closed

Update to stable version of LOST #8939

zugaldia opened this issue May 9, 2017 · 11 comments
Labels
Android Mapbox Maps SDK for Android release blocker Blocks the next final release

Comments

@zugaldia
Copy link
Member

zugaldia commented May 9, 2017

With #8872 and mapbox/mapbox-java#457 we're updating to a SNAPSHOT version of LOST in order to be able to troubleshoot mapbox/mapbox-java#401.

Before we publish 5.1.0 final we need to make sure we update the code to a stable version of LOST, either 2.3.0, or downgrade to the latest 2.2.x stable.

cc: @tobrun @cammace

@zugaldia zugaldia added Android Mapbox Maps SDK for Android release blocker Blocks the next final release labels May 9, 2017
@zugaldia zugaldia added this to the android-v5.1.0 milestone May 9, 2017
@tobrun
Copy link
Member

tobrun commented May 11, 2017

Adding here that we also need to bump to stable versions of the MAS dependencies

@zugaldia
Copy link
Member Author

Closed via #9112.

@tobrun tobrun reopened this Jun 9, 2017
@tobrun
Copy link
Member

tobrun commented Jun 9, 2017

Reopening this as we are now depending on a SNAPSHOT build of LOST since #9142.

@zugaldia
Copy link
Member Author

3.0.1 patch release landed on #9302.

@krsticdragan
Copy link

Hi, I just wanted to report you that I have updated to a latest build 5.1.0-beta.5 and im still getting DeadObjectException and Location update after client was dissconnected. Unfortunatly I cant catch the behivour what cause this exceptions, it happens random thru application.

@zugaldia
Copy link
Member Author

@krsticdragan I don't think lostzen/lost#218 is fixed with the latest patch release. Still, please do share as much information as you can to help us reproduce the problem.

@joaopedro1520
Copy link

The problem is still not fixed with this version, I'm still getting tons of crashes after this update

@joaofyz
Copy link

joaofyz commented Jun 22, 2017

Hi @zugaldia @tobrun ,

We are using the 5.1.0-beta.5 version and we are still getting this crash in our app.

We had 1500 crashes since we updated to this version, 84% of them in the android versions 6 and 7.

Fatal Exception: java.lang.RuntimeException: android.os.DeadObjectException at com.mapzen.android.lost.internal.FusedLocationProviderServiceDelegate.reportLocation(SourceFile:78) at com.mapzen.android.lost.internal.FusionEngine.onLocationChanged(SourceFile:196) at android.location.LocationManager$ListenerTransport._handleMessage(LocationManager.java:297) at android.location.LocationManager$ListenerTransport.-wrap0(LocationManager.java) at android.location.LocationManager$ListenerTransport$2.handleMessage(LocationManager.java:249) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6692) at java.lang.reflect.Method.invoke(Method.java) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358) Caused by android.os.DeadObjectException at android.os.BinderProxy.transactNative(Binder.java) at android.os.BinderProxy.transact(Binder.java:628) at com.mapzen.android.lost.internal.IFusedLocationProviderCallback$Stub$Proxy.onLocationChanged(SourceFile:104) at com.mapzen.android.lost.internal.FusedLocationProviderServiceDelegate.reportLocation(SourceFile:76) at com.mapzen.android.lost.internal.FusionEngine.onLocationChanged(SourceFile:196) at android.location.LocationManager$ListenerTransport._handleMessage(LocationManager.java:297) at android.location.LocationManager$ListenerTransport.-wrap0(LocationManager.java) at android.location.LocationManager$ListenerTransport$2.handleMessage(LocationManager.java:249) at android.os.Handler.dispatchMessage(Handler.java:102) at android.os.Looper.loop(Looper.java:154) at android.app.ActivityThread.main(ActivityThread.java:6692) at java.lang.reflect.Method.invoke(Method.java) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1468) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1358)

@tobrun
Copy link
Member

tobrun commented Jun 22, 2017

@joaofyz thank you for the report. I would highly insist not shipping beta versions of our SDK in production. These pre releases are for test purposes only. Feel free to comment on the actual issue tracking that this here.

@zugaldia
Copy link
Member Author

@joaopedro1520 @joaofyz to insist on what @tobrun just mentioned, the latest patch release of LOST fixes lostzen/lost#213 but it does not fix lostzen/lost#218. Please do report any information that could help us reproduce this issue on lostzen/lost#218.

@krsticdragan
Copy link

@zugaldia @tobrun I hope this info could help you. In my project im not using LOST, im using only LocationManager and setMyLocationEnabled method. Crashes still happends randomly from time to time with no obvious rule.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Android Mapbox Maps SDK for Android release blocker Blocks the next final release
Projects
None yet
Development

No branches or pull requests

5 participants