[Vertex AI] Add CustomNSError conformance to BackendError
#14029
+39
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Added
CustomNSErrorconformance toBackendError. This improves the string returned bylocalizedDescriptionand will also improve interoperability with Crashlytics (e.g., when reporting non-fatal errors, logged errors are grouped bydomainandcode).Example - calling
error.localizedDescriptionintestGenerateContent_failure_invalidAPIKey():The operation couldn’t be completed. (FirebaseVertexAI.BackendError error 1.)"API key not valid. Please pass a valid API key. (com.google.firebase.vertexai.BackendError - HTTP 400 INVALID_ARGUMENT)"#no-changelog