Topic: Bug (+workaround): Transaction data not recognized by armory (0.96.3, 0.96.2) (Read 304 times)
September 28, 2017, 03:21:51 AM
I'm aware of this, should be fixed in the testing branch.
September 28, 2017, 02:56:01 AM
Tested on 0.96.3, but this is probably relevant to versions with the multiple signer options:
Using an offline signer with the 'default' set I get a dialog box saying: "The transaction data was not in a format recognized by Armory."
The transaction remains unsigned.
There is nothing recorded in the log files.
Clicking on the label 'Click here for more information about this transaction' shows the details of the transaction normally.
Workaround: opening the signer dialog box (clicking on 'signer') - there is only the 'default' and the 'C++ signer' radio buttons enabled. Choosing the 'C++ signer', clicking 'Apply' and proceeding with the signing procedure works.
Tested on Win64.
Using an offline signer with the 'default' set I get a dialog box saying: "The transaction data was not in a format recognized by Armory."
The transaction remains unsigned.
There is nothing recorded in the log files.
Clicking on the label 'Click here for more information about this transaction' shows the details of the transaction normally.
Workaround: opening the signer dialog box (clicking on 'signer') - there is only the 'default' and the 'C++ signer' radio buttons enabled. Choosing the 'C++ signer', clicking 'Apply' and proceeding with the signing procedure works.
Tested on Win64.
Jump to: