RE: Unrecognized Error when using UnSigned Offline TX from OmniWallet

[buybuild]

I recently moved a little TetherUS (USDT) to an offline Bitcoin address i created using Armory.

I then added a few watch only wallets on OmniWallet.

Back at beginning of Feb 2019, whenever I tried to create an Unsigned Transaction to send some USDT (TetherUS) from ONE of the watch only wallet, I would get a server error on OmniWallet and it wouldn't generate an unsigned transaction.  It would however work on the other address. 

The lead developer wrote a patch that seemed to fix that. It was some type of error linked to the index number of the bitcoin address used.

However, now when I take the Unsigned Transaction created on OmniWallet for that address to send some USDT from my offline Armory wallet address, there is an error which says UNRECOGNIZED in Armory, when Armory tries to read the unsigned transaction file.

Can someone please help.

I am not sure what the issue is as the unsigned transaction is generated, but now Armory doesn't recognise it.
This only happens with one of the bitcoin address from my Armory wallet.  The others seem to work fine. Really strange.

Thanks

[1714837824]

1714837824

[1714837824]

1714837824

[1714837824]

1714837824

[goatpig]

What version of Armory are you using?

[buybuild]

Armory Bitcoin Wallet: Version 0.96.5-beta-8730390989

Thanks

[goatpig]

You should use the version of Armory specifically designated by your version of OmniWallet of you're gonna get mismatches in offline tx format.

[buybuild]

Hi,

I am using the latest version of Armory and that is compatible according to OmniWallet.

I created a wallet in Armory and obtained 3 BTC addresses from the same seed.

2 of the BTC addresses work perfectly with the latest version of Armory, however the 3rd BTC address throws an error where it doesn't recognise the unsigned offline transaction when created via OmniWallet.

I managed to work with a lead developer of OmniWallet who also believes the error is being thrown in Armory somewhere.

We managed to do a manual transaction from the troublesome BTC address using Coinb.in.

After that was done, the BTC address all of a sudden started to work with Armory.

Very strange situation, but resolved now.

Thanks