Skip to content
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.

getVarint called with unexpected parameters when sending Stealth #1824

Closed
Kryptoxic opened this issue Feb 23, 2019 · 20 comments
Closed

getVarint called with unexpected parameters when sending Stealth #1824

Kryptoxic opened this issue Feb 23, 2019 · 20 comments
Labels
bug Oops, this is a bug

Comments

@Kryptoxic
Copy link

Ledger Live Version and Operating System

Tested on Ledger Live 1.4.1
Windows 10

Expected behavior

The Ledger Nano S should show the amount of XST being sent along with the address that it is being sent to.

Actual behavior

The screen on my Ledger Nano S does not show the address and amount to be sent at all and also, the Ledger Live application show an error message after a while saying "getVarint called with unexpected parameters".

Steps to reproduce the behavior

Simply open up the Stealth account and attempt to send some XST. Upon reaching the screen where the message asks me to verify the transaction on my Ledger device, the screen does not display the amount to be sent and the address it is going to be sent to and the Ledger Live application will show the error message as stated above.

@Kryptoxic
Copy link
Author

Update:

I tested this with the new 1.5.0 update and the issue still persists.

@myselfmyself
Copy link

Same. They mentioned to me a few months ago that they believed the update would fix the problem; has not been fixed. Coins still stuck. Sent them into the ledger just fine, but now cant get them out. Someone please look into this and fix this for your customers/users.

@Kryptoxic
Copy link
Author

Ticket 271821 has been opened with Ledger to nudge them about this issue again. Waiting for their reply. Will update once they replied to my ticket

@myselfmyself
Copy link

myselfmyself commented Mar 9, 2019 via email

@gre
Copy link
Contributor

gre commented Mar 9, 2019

We'll take a look at this ASAP.

@myselfmyself
Copy link

myselfmyself commented Mar 10, 2019 via email

@Kryptoxic
Copy link
Author

We'll take a look at this ASAP.

Thank you for replying. If you would like, you can pick up on my support ticket as well which is ticket 271821

@gre gre added the bug Oops, this is a bug label Mar 16, 2019
@myselfmyself
Copy link

myselfmyself commented Mar 26, 2019 via email

@myselfmyself
Copy link

Please fix so we can access our coins

@myselfmyself
Copy link

myselfmyself commented Apr 14, 2019 via email

@myselfmyself
Copy link

Still no updates and no solutions offered. Problem for over three months now. Can someone not take the time to look into this for the community? Please?

@Kryptoxic
Copy link
Author

Still no updates and no solutions offered. Problem for over three months now. Can someone not take the time to look into this for the community? Please?

Yeah I tried to send XST after the 1.7.0 and still the same issue. When will ledger resolve this? I want to move my XST asap

@Kryptoxic
Copy link
Author

Hey @myselfmyself , just wanted to update you on some news that I heard from ledger on their slack. They have done some work on this issue and had a pull request opened.

LedgerHQ/lib-ledger-core#195

Unfortunately, it is still not working for me on 1.7.0 still

@myselfmyself
Copy link

myselfmyself commented Apr 17, 2019 via email

@myselfmyself
Copy link

Has this been resolved yet, or a date estimated for resolution?

@Kryptoxic
Copy link
Author

I haven't had the chance to try sending XST on 1.8.0 yet, have you tried it @myselfmyself ?

@myselfmyself
Copy link

myselfmyself commented May 6, 2019 via email

@gre
Copy link
Contributor

gre commented May 6, 2019

I don't think 1.8.0 have fixed the situation, we're still looking actively at it, see last statement: LedgerHQ/lib-ledger-core#195 (comment)

@Kryptoxic
Copy link
Author

I don't think 1.8.0 have fixed the situation, we're still looking actively at it, see last statement: LedgerHQ/lib-ledger-core#195 (comment)

I see, do you need to get in contact with Stealth's lead dev? I told them about the pull request and the lead dev said that the change has been made a few months ago

@myselfmyself
Copy link

myselfmyself commented May 6, 2019 via email

@gre gre closed this as completed Feb 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Oops, this is a bug
Projects
None yet
Development

No branches or pull requests

3 participants