if custom connectSrc is provided and this endpoint is not available, TrezorConnect.init returns
{"success":false,"payload":{"error":"Manifest not set. Read more at https://github.com/trezor/trezor-suite/blob/develop/docs/packages/connect/index.md","code":"Init_ManifestMissing"}}
I was able to trigger this error with a fresh installation of MetaMask and pairing it with a Trezor immediately. After restarting the browser, the pairing issue no longer occurs.
if custom connectSrc is provided and this endpoint is not available, TrezorConnect.init returns
It should return a better error.
Example