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 was archived by the owner on Aug 8, 2023. It is now read-only.
I just upgrade to mapbox version 3.2.0.
I test on stable and unstable network. This crash happened when network run slow. Please notice that slow network, not turn off the network completely.
I open application with stable network, wait until map did finish rendered.
Then I switch my network to unstable, and zoom in some area which is doesn't render yet.
It will download the tile image, but it can't because off slow network.
02-18 13:26:44.485 19162-19249/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Unable to resolve host "www.mapbox.com": No address associated with hostname
02-18 13:26:44.490 19162-19215/? E/mbgl: {Map}[Style]: Failed to load sprite: Unable to resolve host "www.mapbox.com": No address associated with hostname
02-18 13:26:44.500 19162-19249/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Unable to resolve host "www.mapbox.com": No address associated with hostname
02-18 13:26:44.500 19162-19215/? E/mbgl: {Map}[Style]: Failed to load sprite: Unable to resolve host "www.mapbox.com": No address associated with hostname
……..
02-18 13:26:48.085 19162-19247/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Unable to resolve host "a.tiles.mapbox.com": No address associated with hostname
02-18 13:26:48.105 19162-19249/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Canceled
02-18 13:26:48.110 19162-19247/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Unable to resolve host "a.tiles.mapbox.com": No address associated with hostname
02-18 13:26:48.110 19162-19215/? E/mbgl: {Map}[Style]: Failed to load tile 7/105/51 for source composite: Unable to resolve host "a.tiles.mapbox.com": No address associated with hostname
02-18 13:26:48.110 19162-19249/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Canceled
02-18 13:26:48.115 19162-19247/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Unable to resolve host "a.tiles.mapbox.com": No address associated with hostname
02-18 13:26:48.115 19162-19215/? E/mbgl: {Map}[Style]: Failed to load tile 7/105/52 for source composite: Unable to resolve host "a.tiles.mapbox.com": No address associated with hostname
…….
02-18 13:26:49.125 19162-19247/? W/com.mapbox.mapboxsdk.http.HTTPContext$HTTPRequest: [HTTP] Request could not be executed: Unable to resolve host "a.tiles.mapbox.com": No address associated with hostname
02-18 13:26:49.125 19162-19215/? E/mbgl: {Map}[Style]: Failed to load tile 7/104/51 for source composite: Unable to resolve host "a.tiles.mapbox.com": No address associated with hostname
At this time, it is not crashed, but when press back to exit app, it will be crashed.
We saw a Fatal signal 11 (SIGSEGV) at 0xdeadbaad previously in a case where a C++ exception was getting thrown through JNI. #4193 prevents that from happening, and I think it might prevent this crash as well. Going to close here since I haven't been able to reproduce it after this change. If you see this issue in 4.0.0 later, please reopen.
I just upgrade to mapbox version 3.2.0.
I test on stable and unstable network. This crash happened when network run slow. Please notice that slow network, not turn off the network completely.
I open application with stable network, wait until map did finish rendered.
Then I switch my network to unstable, and zoom in some area which is doesn't render yet.
It will download the tile image, but it can't because off slow network.
At this time, it is not crashed, but when press back to exit app, it will be crashed.
Many logs like this repeat again and again.
The text was updated successfully, but these errors were encountered: