Ledger troubleshooting

The Casa app supports Ledger Nano S/S+ and Nano X devices. 

Whether you are adding the Ledger, doing a health check, or sending funds from your Casa vault, we send you an email with a link you click, which brings you to the Ledger API, a web interface that allows you to add a signature from your keyset easily. Depending on your browser or other device settings, the web interface may have trouble recognizing the Ledger and will give an error message. The following error is a common issue with the Ledger:


Error. TypeError: undefined is not an object (evaluating 'transport.decorateAppAPIMethods')

If you get this error or another error, don't fret! There are a few troubleshooting steps you can try that may help you with this issue.

Checking the firmware

First, please check that you're running the latest firmware on your Ledger device by connecting it to the Ledger Live app:


For detailed instructions on updating the firmware on the Ledger, please see Ledger's support article on updating the device firmware.

Once you've updated the firmware, navigate back to Casa app send a new fresh email, and try the signing process again.

Using BTC Legacy app

Normally, you open the BTC app on your Ledger device to complete health checks or sign transactions with Casa.

If you are upgraded to the latest firmware on your Ledger, but your transaction fails to sign, you may attempt to use the "BTC Legacy" app within your Ledger device instead. 

You can download the BTC Legacy app onto your Ledger by connecting your Ledger to Ledger Live. When prompted to connect, unlock, and open the BTC app on the Ledger, open the "BTC Legacy" app on the Ledger instead. This is a troubleshooting step only - the BTC Legacy app should not normally be needed to sign transactions.

Selecting the device

Make sure to highlight or click on your device when the popup comes up before clicking Connect. If you do not see this window, try clicking the lock icon, but if you still cannot see it, you will need to use a different browser.


Trying a different browser

If you still have issues after updating the firmware, it's possible that some of your web browser's settings are preventing the Ledger from being recognized.

Chromium-based browsers like Chrome and Brave tend to work the best with our system. If you're using Chrome, for example, try Brave. Please note: Firefox is NOT supported for Ledger devices.

Other troubleshooting steps

If you've tried multiple browsers, it could be a different issue. Please try the following troubleshooting steps to get the Ledger to be recognized:

  • Close out any other apps that might be using the Ledger (e.g., Ledger Live).
  • Reboot the computer you're using to connect.
  • Make sure no other USB devices are plugged in when performing a health check.
  • Open the link into "incognito mode" or equivalent.
  • Close the browser, unplug the Ledger, start the browser back up again, and then plug the Ledger back in.
  • If your computer is running Windows 8, please upgrade your operating system.
  • If your computer is running Windows 10, you may need to update a default settings flag in Chrome, by following these steps:

Another thing to consider is your USB cable connecting the Ledger. Not all USB cables are rated for data transfer, so make sure that the USB cable you're connecting is the one that came with the Ledger, or is otherwise rated for data transfer (not just a charging cable).

0x6f00 error

If the previous steps have not resolved this specific error for you, it could be that you are trying to send to a Taproot address. These are very long and begin with "bc1" and they are not currently supported in the Casa app for signing with Ledgers.

As a workaround, you could send the transaction first to your Pay wallet, then on to the Taproot address. Otherwise you will need to send to a different address format to complete the transaction.

@1 address error for ETH

If you scan the QR code for the ETH address in Casa app using a webcam or other device, it may come up as an address with a "@1" on the end. This is a feature of the network that allows differentiation between network layer levels. A workaround to this is to copy and paste the plain text of the ETH address rather than scanning the QR code.

If you've tried the above steps and are still having issues, please reach out to our support team, and we'll be happy to assist. 

Articles in this section

Was this article helpful?
1 out of 1 found this helpful