-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Update to stable version of LOST #8939
Comments
Adding here that we also need to bump to stable versions of the MAS dependencies |
Closed via #9112. |
Reopening this as we are now depending on a SNAPSHOT build of LOST since #9142. |
3.0.1 patch release landed on #9302. |
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. |
@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. |
The problem is still not fixed with this version, I'm still getting tons of crashes after this update |
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.
|
@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. |
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
The text was updated successfully, but these errors were encountered: