-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
SKU SDK: Credentials refresh is forced due to request id conflict #35742
SKU SDK: Credentials refresh is forced due to request id conflict #35742
Comments
Cross-reference: #35158 (where it currently looks like it doesn't work, necessitating this issue - or maybe they're separate/nuanced issues?) |
I'm going to reopen this as there are actually two cases and so far we've only solved the first one:
After consulting with @husobee, we've decided that we will have the server return HTTP status 409 Conflict in the request id conflict case and modify the SDK to automatically regenerate the request id when this status code is returned. |
The above requires |
Verification
Steps:
Confirmed background auto-renewed credentials obviated/removed the session-expired message
|
Description
Users are prompted to refresh their credentials due to the background refresh failing with a request id conflict
Steps to Reproduce
Actual result:
Notice that the refresh notification is triggered despite using a single device.
Expected result:
The background refresh should succeed and the subscription should be usable.
Reproduces how often:
Always
Desktop Brave version:
Android Device details:
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: