Catch errors in debug token exchange logic #8792
Merged
+57
−17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The internal
getToken()
method should never throw - it's used by other product SDKs (auth, etc.) and it's up to those product SDKs to handle errors, which are attached to the token as a string property. We have a try/catch around the exchange logic for the normal token, which returns a dummy token and the error string when an error is caught, but we didn't have this same try/catch around the logic where we try to exchange the debug token. Added it.