-
Notifications
You must be signed in to change notification settings - Fork 916
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
Surface all App Check errors in public getToken() method #8842
Conversation
🦋 Changeset detectedLatest commit: f5a1e4d The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Report 1Affected Products
Test Logs |
@@ -54,7 +55,8 @@ const ERRORS: ErrorMap<AppCheckError> = { | |||
[AppCheckError.STORAGE_WRITE]: | |||
'Error thrown when writing to storage. Original error: {$originalErrorMessage}.', | |||
[AppCheckError.RECAPTCHA_ERROR]: 'ReCAPTCHA error.', | |||
[AppCheckError.THROTTLED]: `Requests throttled due to {$httpStatus} error. Attempts allowed again after {$time}` | |||
[AppCheckError.INITIAL_THROTTLE]: `{$httpStatus} error. Attempts allowed again after {$time}`, | |||
[AppCheckError.THROTTLED]: `Requests throttled due to previous {$httpStatus} error. Attempts allowed again after {$time}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit, these should be transposed to match the order in ErrorParams
and AppCheckError
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Flipped it around the other way on the other two since logically I guess the "initial throttle" should come first.
Size Analysis Report 1Affected Products
Test Logs |
@hsubox76 Thank you for addressing this promptly. May I ask when we can expect this fix to be released? |
The two main changes here are
getToken()
method. Errors here should not block 2P calls to App Check (internal calls from Auth, Firestore, etc)I've also decided to stop logging getToken errors with
console.error
- these should all be thrown by the publicgetToken()
now, and the internal products calling getToken internally (Auth, Firestore, etc.) have access to the error message in a property of AppCheckTokenResult which they can log in the format they choose.Fixes #8822