[Bug report]: Firefly and Firefly Shimmer in Combination with Ledger Nano S (without plus) Transactions cannot be send

CrashOverride-lab commented 1 year ago

Platform

Desktop

Version

Firefly Shimmer (2.0.1) and Firefly IOTA (1.7.1)

Description

Hi Guys,

i and some other Guys have an Interesting Problem with IOTA Firefly and Shimmer Firefly and Ledger.

Problem: Mostly (but not only) when a Wallet hast more then 70 Receive Adresses the Problem occures, that on validating a Transaction (Send IOTA/SHimmer or Staking) --> The process will begun, Waiting on Ledger to confirm but mostly before and sometimes after this Process Firefly report for 1 Second "A Error has occurred". Then Firefly closes the Transaction Window (Firefly itself stayed open and we can open Firefly Setting etc.pp). But the Firefly Error Log is emtpy...

A strange Problem. And it requries mostly 10 attempts for a single Transaction to get thorugh the Process without Problems.

On Shimmer Firefly it has another effect. The amount of tokens who should be send in the failed transaction process will be deducted from the total Balance of the Wallet. A Crosscheck on the Tangle Explorer revealed, that in the Tangle it is the right amount on the Adresses and simply is wrong displayed in Firefly...

Environment:

newest Firefly Shimmer (2.0.1) and Firefly IOTA (1.7.1) Version.
Wallets created with a Ledger Nano S (without Plus) (newest Firmware and Software)
only original USB Cables for Ledger are used
Windows 11 as Base Operating System.
only on IOTA Firefly: The Problem begins if the Amount of Receive Addresses of the wallet exceeds approx. 70 Addresses. From then on it becomes more and more likely that the Problem occurs more and more often.

An interesting Hint seems the Ledger Nano S to be. All Guys had the old Nano S. Maybe a compatibility issue?

Problem-Scope: currently 5 other People can confirm this Problem

Expected behaviour

That it Works would be a nice start :-D

Actual behaviour

see Error description

Can the issue reliably be reproduced?

Yes

Steps to reproduce the issue

see Error description

Operating System

Windows

Diagnostics

From one Client:

Version 1.7.1
Sprache: de
Währung: USD
Node-Auswahl: Manuell
Plattform: win32
Plattformversion: 10.0.22621
Plattform-Architektur: x64
CPU-Anzahl: 24
Gesamtspeicher: 32488.7 MB
Freier Speicher: 20621.3 MB

-----------

FYI: This Problem exists with Node Selection Auto (IF Nodes) and Manual (Community Nodes)

Developer Profile

No

Profile Type

Hardware (Ledger)

Staking

Previously staked

Crash Status

None of the above

Error Messages

Only displaying a short time: "A Error occured"

Another hint: On trying to stake the Amount of IOTA, the Message Box "Confirm Transaction" displays a wrong amount to stake (only 16 MI, but on this Wallet are a view GIs). This Windows will show up for ca. 1-5 Seconds until it closes automatically and the Error Message appears.

The LEdgers on the other way don´t ask a confirmation Input from the User.

Error Logs

Error Logs on Firefly empty.

Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Tuditi commented 1 year ago

It's important to keep in mind that with Ledger nano S the max. supported outputs per transaction is 16 (with Ledger nano S + and X it's 128). This means that if you made a lot of transactions previously, you need to consolidate those manually (for now).

You can do this by checking the different outputs per address on https://explorer.iota.org/mainnet and creating internal transaction to yourself. You can calculate the required amount by summing the amount s of 16 (unspent) outputs.

Tuditi commented 1 year ago

Further investigation of slow address generation on Windows is blocked by: https://github.com/iotaledger/firefly/issues/6427

MarkNerdi996 commented 1 year ago

Tracked in https://github.com/iotaledger/firefly/issues/6429

iotaledger / firefly