Closed aaroncox closed 1 year ago
This is strange because when I login using non-EOS accounts and try to sign the other test transactions on the web UI, the correct chain and account are selected. I haven't looked into it, but is it possible that the autocorrect plugin is setting the esr chain to be EOS?
This should be resolved with the next release of the autocorrect plugin.
It was recreating the ESR payload and losing all the data except the transaction in the process!
Closing it here, since it's not a wallet plugin bug.
I haven't looked into this, but when I use the autocorrect feature for the
wharftt21111
account on Jungle4 to purchase ram, the request that comes in defaults back to EOS and then uses the wrong account.