[ICE: 9] Troubleshoot Fireblocks wallet issues

[just-a-node]

Background

Major clients using Fireblock haven't been able to start bridge transactions.

Some users get stuck loading Fireblocks from the wallet selection. Select "Connect wallet" -> "All Wallets" -> Search for Fireblocks:

• In the "Mobile" tab, they see this screen loading forever:
  • 
• In the Webapp tab, they see this screen with no other prompts:
  • 

Users who have been able to connect see an infinite loop of "Checking approval" spinning in the UI when they click "Send". This stops after a few moments and the "Send" button reappears.

Tasks

• [ ] Fix Fireblocks being able to connect to Mobile/Webapp
• [ ] Fix transactions not popping up when bridge transaction is sent

[just-a-node]

Tried Fireblocks mobile connection with Android app. After selecting "Link Device" -> scan QR code, got this error: "Unknown QR code, This QR code does not belong to Fireblocks"

[just-a-node]

Tried Fireblocks webapp connection. After opening the link in the popup "Continue in Fireblocks", it opens a link to https://console.fireblocks.io/v2/wc?uri=wc%3A6f8704012a756520ede2c32733c9c164551c31da9b28bc4fe8dccfeefa55b8b3%402%3Frelay-protocol%3Dirn%26symKey%3D3b1c20435c0ab4ba1c62ca6929d99d36c262e15da4fca11bb56bee25225a977d with a login screen. Since I've only been able to get a sandbox environment at https://sandbox.fireblocks.io/v2/web3, this login page doesn't work.

[alexwhte]

Next step: @just-a-node try to work with both Walletconnect and Fireblocks support continue working with Fireblocks support team

[just-a-node]

Call with BTCapital:

• Seeing an "allowance" error in the console causing a revert exception error on the UI
• Tried approving ezETH directly to the Lockbox via Etherscan and then sending the bridge transaction after approval had been completed - same results
• Tried transaction through incognito, clean browser with no other extensions - same result
• Tried bridging ETH on the same path - this worked fine

[just-a-node]

We have raised the issue with the Fireblocks and asked them to dig into Maven's backend logs to see if the "Fireblocks doesn't support the dApp's requested asset (100)" error is present and if there's any additional troubleshooting support they can help with from their side.

We have also asked Maven + BTCapital to raise support tickets.

Attempting to reproduce this from our own setup + Firebase console has not been successful.

[alexwhte]

moving to backlog... will need to check again with an active issue/user