[HOTFIX] Browser: handle unsupported URLs

[jpcloureiro]

Description

In-App browser do not handle special URLs (deeplinks like market://details?...)

Change from native URL API to url-parse package.
This allows the app to handle unsupported URLs instead of throwing an error.

Screenshots/Recordings

Screen that will appear when the user tries to use a special URL / deeplink inside In-App browser

Issue

Progresses #5794

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[Gudahtt]

We are already using this polyfill: https://github.com/charpeni/react-native-url-polyfill which apparently follows the whatwg standard for URL, which does support custom protocols. I'm curious to know which specific scenario is failing that url-parse fixes.

[jpcloureiro]

We are already using this polyfill: https://github.com/charpeni/react-native-url-polyfill which apparently follows the whatwg standard for URL, which does support custom protocols. I'm curious to know which specific scenario is failing that url-parse fixes.

Invalid URL error handling needs to be implemented before replacing parse-url with the native URL API.

In this case market://details?src=io.metamask. ... deeplinks are transformed into an invalid URL in the form of null?src=io.metamask.

url-parse being designed to not throw errors (like legacy nodejs url API) keeps the app from crashing

This hotfix will prevent users from being stuck on the error boundary screen.

A proper way to handle URLs should be implemented next

[Gudahtt]

deeplinks are transformed into an invalid URL

Ahhh I see. I thought you meant that new URL was throwing directly. That makes more sense.

[andreahaku]

LGTM

[chrisleewilcox]

@jpcloureiro what is expected if user has coingecko app installed on device? Will coingecko app open? Can you confirm this? Will need this confirmed in development before handing this over to QA.

[chrisleewilcox]

Please review my comments about behavior for coingecko app on device.

[jpcloureiro]

@chrisleewilcox
In 5.14.0, the browser presents the "Something went wrong" screen regardless of having the coingecko app installed or not.

I would say this is the expected behaviour for this PR as well.