-
-
Notifications
You must be signed in to change notification settings - Fork 204
stellar: send does not work #447
Comments
Yes, exactly the same issue with T1 also:
|
I already reported it to Stellar devs here: stellar/go#795 |
Will do on Monday |
Summary:
So in a nutshell, I don't think this is an error on the firmware side. It might be the case for the ChangeTrustOp, which I'll investigate as part of #421. |
What confuses me a little is that I'm not getting the same behaviour as reported by the reddit user and @pankrats. I can confirm the behaviour by @reqlez here: stellar-deprecated/account-viewer#70 (comment) But let's see if we succeed to update the account viewer. |
Seems fixed 🎉. @bosomt could you pls check if it works for both T1 and TT? I've tried with T emulator only |
I have a T, instructions to test? if you want I can do that as well. is this now live on trezor.io/stellar ? |
Sure, if you want just give it a go. trezor.io/stellar should be working now |
Actually, just tested with T and Chrome ( wihout the bridge software installed, if that matters ). Works great ! May I suggest getting the inflation destination code on the page going as well ;-) |
Apparently, there is still an issue with the account viewer when sending to a different address than yours. I'll investigate |
I sent to a different address when I tested... |
There was a problem with addresses that did not have any lumens on it yet. The Payment op was called instead of the CreateAccount op. We already have a fix and it will be deployed soon. I'll close this issue then |
Fix deployed. Try trezor.io/stellar whether it works. |
consider it fixed. |
Confirmed 🎉 |
https://www.reddit.com/r/Stellar/comments/abynfg/send_fails_with_stellar_account_viewer/
We have to check this, whether this is correct and whether it affects T1 or not.
The text was updated successfully, but these errors were encountered: