2

On all other operations I can use a different 'Source Account', but if I try to do it on 'Manage Data', I get:

  • 'tx_failed' when sending with Python-sdk
  • no changes applied to XDR if I try it in Laboratory web interface

Am I doing something wrong or is there a bug with transaction builder?

4
  • It works in the Laboratory transaction builder web interface for me. If I add a source account to the operation, the XDR gets longer. Moreover, I can verify that the right thing is happening by pasting the generated XDR into stellar-core --base64 --printtxn -. You must be doing something else wrong, or maybe not pasting a syntactically valid account ID. More information? Jun 19, 2018 at 22:27
  • Thank you @user3188445 for your time! You are saying that it works in transaction builder web interface, however for me it does not. On other operations it works except on 'Manage Data'. Did you try it with 'Manage Data' operation? I uploaded a video showing how the XDR string does not change when I change 'Source Account'. link I am stuck, dont really know how to solve it. Thanks!
    – Linas
    Jun 20, 2018 at 10:51
  • Oops, somehow you said Manage Data and I managed to read SetOptions. You are correct that this is a bug in Stellar laboratory. Jun 20, 2018 at 16:38
  • Should be fixed after merging github.com/stellar/laboratory/pull/335 Jun 25, 2018 at 17:21

1 Answer 1

0

This bug has been fixed: Laboratory

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.