I cant send any tokens from Metamask or Rabby. Error like: "• Invalid parameter “path” (= undefined): Expected required property
I tried reinstalling the firmware, reinstalling Trezor Bridge, updating the MacBook, tried from a different browser. But the trezor suit works
I am having the same issue.
Hi @Hodlerx and @psilocyben,
Please try clearing your browser’s cache or using incognito/private browsing with your third party app when connecting your Trezor.
If you are still experiencing challenges connecting your Trezor to third party apps please create a support ticket through our Chatbot Hal.
i created a new profile and installed a fresh metamask and it seems to work for signing tx.
there’s something still funky/broken and definitely pretty co-incidental about the timing with Hodlerx (maybe a chrome update broke something?).
anyway thnx @nickw i’ll take it from here.
ok so mine is now fixed inside Rabby as well… just to follow up here for anyone (@hodlerx) who finds this, the check box of “don’t ask me again” about the export of the public keys is poison (note: the public key export process did not happen previously when this failed). i’ve had troubles before with it and they seem to expire or desync in some way and requests start to fail ungracefully (the public key export request never happens)… i’ve noticed that if i don’t tick this box nothing like this ever happens.
i had to re-add the hardware wallet inside rabby, which prompted me for the key… the transaction signing process then went smoothly.
if i could recommend to the devs finding a better handling for this process or removing the “don’t ask me again” feature, that would be neat.
cheers.
Hi @Hodlerx, can you please open a support ticket and provide the log?
Open this page before Metamask wallet to start logging your session: https://connect.trezor.io/9/log.html
Then add the log to the ticket. Thank you.
I have the same issue as well, but only with rabby wallet. Metamask worked fine.
Same here - MASSIVE problem. Really need the team to do something here, I believe it must have been the latest FW update (sending from Trezor Suite works, but none of the browser wallets work)
Hey there, i’m facing the exact same issue and want to give your solution a shot - is there any risk in “re-adding” the wallet? what’s the process exactly? Deleting the current one and then simply re-adding the address and going through the setup again?
As long as you are custodying all of your addresses on Trezor and not your software wallet, there is no risk. Your private keys remain on the Trezor, only the information about your wallet stored on your third party wallet (such as public keys) is deleted.
