-
-
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
[BUG] Can't load tiles: ClientException with SocketException: Connection attempt cancelled #1761
Comments
Hi @DEGoodmanWilson, |
I'm going to group this as closeable by #1742. If it isn't resolved by it, then we can reopen this! |
@JaffaKetchup: #1742 certainly improved this issue, I see it a lot less frequently when building my app against
Sample Error Stack
Interestingly, if I trigger the error, but then continue repeating the steps above, I'll start to see this error in the mix:
Suggesting that perhaps there's an issue with freeing file handles for network images that fail to load, too? |
That's likely a slightly different issue. Mapbox starts rate limiting after a while and gets very slow. If you're zooming in and out, the HTTP connections will stack up and stack up waiting for their turn to get a response. |
Thanks for the suggestion! Adding |
What is the bug?
I have implemented a very basic map view in an app—for several months, the map has operated as expected. But with 6.1.0, I am receiving a large number of "ClientException with SocketException" errors whenever I load the map, and no map tiles show. Panning the map doesn't help, but zooming the map often does trigger the tiles to load. I have attempted several tile providers, including OSM's open service and Lima Labs, so I know the problem isn't the tile provider. It has happened with my beta testers, so I know it's not my own network.
I tried using
CancellableNetworkTileProvider
, but the same problem persists…although the exceptions stop being thrown.I suspect the issue may be related to #1698 but I can't be entirely sure.
How can we reproduce it?
Yes, just this simple…
Do you have a potential solution?
No response
Platforms
iOS 17
Severity
Erroneous: Prevents normal functioning and causes errors in the console
The text was updated successfully, but these errors were encountered: