-
-
Notifications
You must be signed in to change notification settings - Fork 860
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
handling tileProvider errors #536
Comments
hmm it doesn't crash it on mine (I have a pull request that "may" help with that, not sure), but I suspect could be handled better...does it trigger a crash in release mode, and is it possible to include the code to replicate ? It may be worse on certain tileproviders. |
ididint try it on release mode , but in debug mode try to use NonCachingNetworkTileProvider and zoom in more and more until the server could not get an image and it will throw eception |
In the interim, to get around that problem, maybe set a min/maxzoom, to prevent that problem. But naturally we don't want it to crash still, just handle it gracefully. |
yes i already did but for cachingNetworkTile i cant handle that |
It may be useful to post the output of the crash btw, just to see which bit is causing it, maybe that provider can wrap the request in a try clause or something. |
════════ Exception caught by image resource service ════════════════════════════ When the exception was thrown, this was the stack |
I have same error |
sometime tileProvider cause stopping of the app because of the remote server cant return a response or the cachingNetwork cant find a file but i didn't find a way to handle these errors to avoid the crash of the app
The text was updated successfully, but these errors were encountered: