Signing a transaction with Ledger fails if the transaction is "too" big

[frol]

Certain transactions like those that involve contract deployment or huge blob of arguments in a function call read to an obscure error, which was already reported here near/near-cli#612 and here LedgerHQ/app-near#13

There is no solution yet. Further discussion should happen in the thread mentioned above.

[frol]

It is an implementation of on-Ledger app (https://github.com/near/app-near), which is limited by the memory constraint of Ledger device (4KiB of RAM). NEAR app on Ledger allocates 650 bytes for the transaction buffer, and so it is a hard limit at the moment unless someone implements some streaming mechanism: near/near-cli#612 (comment)

[0x3bfc]

Same issue here while using the deploy action for deploying contract where it is signed by ledger.

near contract deploy <MYACCOUNT_ID> use-file /tmp/contract.wasm without-init-call network-config testnet sign-with-ledger --seed-phrase-hd-path 'm/44'\''/397'\''/0'\''/0'\''/1'\'''
Error: 
   0: Error occurred while signing the transaction: APDUExchangeError("Unknown Ledger APDU retcode: 27024")

Location:
   /Users/ahmed/.cargo/registry/src/git.luolix.top-1ecc6299db9ec823/near-cli-rs-0.5.1/src/transaction_signature_options/sign_with_ledger/mod.rs:97

The main issue is mainly related to the near-app for ledger (Nano S plus was used).