-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add retries to API to mitigate network error #100
Labels
enhancement
New feature or request
Comments
mcorner
added
bug
Something isn't working
enhancement
New feature or request
and removed
bug
Something isn't working
labels
Apr 3, 2024
@mcorner |
We are in the process of releasing a stable version of 18.5.0 as we speak. Shortly after that we will have an 18.6.0-beta01 that will contain the new API. Android will be first, within about three weeks. Then iOS will follow shortly. We look forward to your feedback and hope that you find this API easier to integrate. |
thank you very much for the feedback |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The API for getClient will fail in conditions of no, or poor networking. The nature of the SDK is that it needs to be connected to initialize and retrieve a token from execute.
Our current proposal is to create a new API that will not require networking during initialization, but will begin the process in the background. It will wait for a network connection and automatically retry if needed.
When subsequently calling execute the new API will wait for this initialization to complete up to the timeout (or infinitely if specified) and return an error if initialization or token retrieval cannot be completed in time.
We feel that this will be easier to use and relieve the burden of retries from the implementor.
Suggestions are always welcome.
The text was updated successfully, but these errors were encountered: