You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when an error happens due to NVM corruption we just return an error to the APDU, this is because this code was made before we had UI in rust so this was the simplest (and correct) way to handle these kind of issues.
Now that we do have UI in rust, it would be very friendly if we could somewhat display this issue on the screen, so that the user can see what the problem is and also aid in troubleshooting (ie if the screen shows "NVM corrupt" the user needs to change their device)
Not sure this is related to #167 that much, as these are 2 different situations:
display entrypoint is while showing the transfer operation, where we show the amount fees etc,
this issue is not a "normal" state, like the entrypoint it
Currently when an error happens due to NVM corruption we just return an error to the APDU, this is because this code was made before we had UI in rust so this was the simplest (and correct) way to handle these kind of issues.
Now that we do have UI in rust, it would be very friendly if we could somewhat display this issue on the screen, so that the user can see what the problem is and also aid in troubleshooting (ie if the screen shows "NVM corrupt" the user needs to change their device)
Related issue: #97
See
ledger-tezos/rust/app/src/handlers/baking.rs
Line 144 in ef44255
ledger-tezos/rust/app/src/handlers/baking.rs
Line 179 in ef44255
🔗 zboto Link
The text was updated successfully, but these errors were encountered: