#RC#
Interacting with automated protocols requires a precise alignment of network settings and wallet data. If the ledger-live-common interface feels unresponsive, try clearing your browser’s local storage. A proven solution is to use a private RPC endpoint instead of the default public gateway. The sudden appearance of a „fetch error“ is usually a temporary node glitch.
Running ledger-live-common on a mobile device might lead to slower signing times due to resource limits. Most minor glitches are resolved automatically once the global network congestion subsides. An outdated web3 provider is often the hidden reason behind many failed dApp interactions. A conflict between the dApp and the browser’s storage can cause the interface to freeze.
A mismatch between the wallet’s gas estimation and the contract’s needs can lead to failure.