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
getZoom and getVisibleBounds never resolve on Android #1353
Comments
Any update on this ticket. I am facing same problem. "@mapbox/react-native-mapbox-gl": "6.1.2-beta2" Please suggestion any work around if possible. |
Okay, i have got some help from stackoverflow. there is some problem in mapbox library itself. I can see some log related with bounds with command
So when we create apk with this code it will work fine. but not working with debug mode which create big problem for implementation of further work. You can review stackoverflow link that question i have asked. Can we get quick solution with debugging mode too? |
i met the same problem ,the production environment do not work too. is there any solution? |
In my case this method doesn't work. It never returns any response. |
I can't confirm it. In my cases this is woking fine.
@nitaliano can be closed. |
getVisibleBounds() is only working when in debug mode. when I switch off the debug connection the app freezes when it hits this._map.getVisibleBounds(). |
As you can see in the code above i have no problems. It's tested in debug and release builds. |
When I debug native code, everything works well, but as soon as I stop the debugger, and re-run the application, the module functions don't resolve. |
Calling this.map.getZoom() and this.map.getVisibleBounds() never resolve to the values requested. The map object is ok, the function call works allright but it just hang and never resolve. It doesn't throw either.
On Android.
deps :
"@mapbox/react-native-mapbox-gl": "^6.1.3",
"react": "16.3.1",
"react-native": "~0.55.2",
Any leads ?
Note : This comportement only appear when my app is connected to development server
The text was updated successfully, but these errors were encountered: