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.
Create a new offline region of any size using a style that relies on Mapbox-hosted sprites and tilesets.
Start downloading it.
Watch for error message Failed to load sprite: HTTP status code 429
Expected behavior
SDK does not trigger API rate limits.
Actual behavior
Sometimes, but not always, you see the 429 response, which must mean that the SDK is kicking off requests faster than the API allows.
Question
We are killing the offline download whenever an error occurs. For errors like this, does the SDK retry downloading the asset after reporting the 429 response, or is killing on the first error the correct way to handle them?
The text was updated successfully, but these errors were encountered:
We need to add an enumeration value to Response::Error::Reason representing a rate-limiting situation, include the value of any Retry-After response header somewhere (with a fallback to the non-standard x-rate-limit-reset header used by Mapbox APIs), and handle this situation in OnlineFileRequest by retrying according to the specified Retry-After value or a reasonable default.
Platform: Android
Mapbox SDK version: 4.1.0
Steps to trigger behavior
Failed to load sprite: HTTP status code 429
Expected behavior
SDK does not trigger API rate limits.
Actual behavior
Sometimes, but not always, you see the 429 response, which must mean that the SDK is kicking off requests faster than the API allows.
Question
We are killing the offline download whenever an error occurs. For errors like this, does the SDK retry downloading the asset after reporting the 429 response, or is killing on the first error the correct way to handle them?
The text was updated successfully, but these errors were encountered: