-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: LocationLayer Plugin 3.0 #266
Comments
@psinetron cc @cammace |
Yes when |
#265 I got the same issue and reported yesterday. |
Yes. A similar problem.
|
@psinetron can you move your permission check before |
@cammace yes, thank you. I moved check, but this does not fix the problem. All permissions is granded |
Error again.
|
@tobrun @cammace I believe I have a similar issue here. I have a fragment that has a MapView, and another fragment that shows stats about the user's progress on a hiking trail. When I switch to the stats fragment, I need to pause the LocationLayerPlugin since the MapView is no longer in focus to provide UI updates, but I need to keep tracking their location (via the LocationEngine) to continue validating the user's position. The LocationLayerPlugin's onStop() method works fine, but I get an error when invoking onStart() from the MapView fragment's onStart() method. Below is what I see in the logs after the crash:
Here's how I am starting the LocationEngine and LocationLayerPlugin, and invoking onStop() and onStart():
I've also tried handling the runtime exceptions without @SuppressLint, but no luck. I'm using the following Mapbox dependencies:
Any help on this would be greatly appreciated! |
Now that 6.0.1 of the Map SDK and 0.5.0-beta.2 is available with significant changes on both ends, I'd love if you guys could retest this issue and see if it still exist. |
For now, i'm closing this issue but can reopen if the issue still exists even after updating. |
For everyone having this issue. I tried to fix this bug in my projected with the 0.5.0-beta.2 version. I changed the following points compared to the previous version where I used the LostLocationEngine:
I use the map in a fragment and use Android architecture components. I hope these small points will save you guys some time. |
Thanks! Will test tomorrow |
@psinetron how did it go? |
after updating to 0.5.0 I get the error: Error:(95, 5) error: resource style/LocationLayer (aka my.bundle:style/LocationLayer) not found. |
@marconealberto Change the style resource name to |
Often bug when App stoped and started
The text was updated successfully, but these errors were encountered: