Safely handle bad URIs when tracking deep links #767
Merged
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.
as per #736, when tracking deep links with a bad URI it causes the app to crash. The error stems from android being able to accept a non-hierarchal URI for opening the app, but unable to parse the info using
getQueryParameterNames()(eg of bad uri:wc:f94d4c5b-a28e-a516-4fd7-2bf37eca3a9e@1bridge=https%3A%2F%2Fbridge.walletconnect.org&key=ccaac40bbc0b9bd17d6ee8ff58f3ccfe3e)This change will make it so that we do not crash the app, while tracking the deep link, but not parse any of the URI details
Closes #736