aaroncox
commented
5 years ago Apologies for the delay on getting back to you on this one.
In the cold wallet, if you swap over to Tools -> Manage Wallets, then using the dropdown on the right column of the account in question, is it showing one of the public keys associated to the account?
I ran a few tests trying to reproduce the issue - but wasn't able to. I have a few other things to investigate, but knowing that the proper key is loaded for the account will be good to know.
JohnAlf
After creating new WORBLI Active account in the Watch wallet with public key, Updating Staked WBI and saving the unsigned transaction to disk, creating a new WORBLI account in the Cold wallet using the Active Private key, signing the transaction and returning to the Watch wallet and importing the transaction, I receive this error:
Error 500,"message"."Internal Service Error","error".{"code".3090003,"name"."unsatisfied_authorization","what"."Provided keys, permissions, and delays do not satisfy declared authorizations","details".[{"message"."transaction declares authority '{\"actor\".\"myamazingwbi\",\"permission\".\"active\"}', but does not have signatures for it under a provided delay of 0 ms, provided permissions [], provided keys [\"EOS5d9XJJcGtpxJ9PunCRKbJZnNUPWfgseCxTnQjQTqQiJKkjrbVv\"], and a delay max limit of 3888000000 ms","file"."authorization_manager.cpp","line_number".520,"method"."check_authorization"}]}}