Using non-official Ledger apps is no longer supported

[Zarigis]

As of 0.93.98, Rabby will now only sign transactions from the official Ethereum app, breaking any workflow that involves using custom apps on the Ledger itself. Now, if I have a custom Ethereum app open, Rabby tries to switch to the main Ethereum app instead of actually submitting any transaction requests.

[dmy147]

Thanks for the feedback. This behavior is expected following our migration to Ledger DMK and @ledgerhq/device-signer-kit-ethereum.

Rabby’s Ledger integration works with the official Ethereum app. Custom Ledger apps are currently outside our supported security model, so Rabby will switch to the official Ethereum app before sending signing requests.

We understand this may affect existing custom-app workflows, and we appreciate you bringing it to our attention.

[Zarigis]

For anyone else in this situation, you can work around it by changing the expected app name. The source file is src/background/service/eth-ledger-keyring.ts and the constant name is ETH_APP_NAME. In the compiled javascript, it's in the background.js file, where you need to change the text td="Ethereum" .