You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
I'm working with Mapbox version 5.0.2 but I got a weird dialog with the message "Unfortunately, App has stopped" without the application crashes.
And I don't have no specific message in Android Monitor that explain this one.
I already add mapboxMap.setMyLocationEnabled(true) in onMapReady to show user location drawable on the map.
@Override
public void onMapReady(MapboxMap mapboxMap) {
/** set Max Zoom Preference**/
/** set Min Zoom Preference**/
mapboxMap.setMyLocationEnabled(true);
}
The text was updated successfully, but these errors were encountered:
@13kz did you request any runtime location permissions? How do you mean no specififc messages in your android monitor? If the app crashed there should always be stacktrace. Sometimes it's hidden under your logcat filters. Without having any stacktrace this issue isn't actionable for us. The test activity we the same code works as expected on master.
@tobrun, u're right. The stack trace is visible when I change Debuggable process in Android Monitor. This issue is already created here (lost issue).
I'll use Release Android v5.1.0-beta1 version to check.
@13kz, beta1 will not resolve your issue yet. The PR in #8872 will fix this. Feel free to retest when that lands with a SNAPSHOT or when beta.2 is released (eta somewhere this week). Closing this as a duplicate of #8639
Platform:Android
Mapbox SDK version:5.0.2
I'm working with Mapbox version 5.0.2 but I got a weird dialog with the message "Unfortunately, App has stopped" without the application crashes.
And I don't have no specific message in Android Monitor that explain this one.
I already add mapboxMap.setMyLocationEnabled(true) in onMapReady to show user location drawable on the map.
The text was updated successfully, but these errors were encountered: