ChangeRegistration can respond with result = UNSUPPORTED_RESOURCE #3091
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
jacobkeeler
approved these changes
Oct 22, 2019
iCollin
deleted the
fix/change_registration_responds_unsupported_resource
branch
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.
Fixes #1694
This PR is ready for review.
Risk
This PR makes minor API changes.
Testing Plan
Manually
Summary
The ChangeRegistration Response in the MOBILE_API lists a few different possible resultCodes that can be returned but does not list UNSUPPORTED_RESOURCE as one even though this can be returned. (by sending an unsupported ttsName for example)
Changelog
Enhancements
CLA