Under certain conditions, Remote Account can not be deactivated.

[mizunashi]

General account: NCVGXT-CV7YYG-CUTOWR-SEALEV-HVTDFR-J54BQY-DKTI Remote Address on above: NABDQJNFSEHPOMWEQLSXMEPT3Y2KF3IXII57GTXU

Account changed to Malti-sig later: NCVGXT-CV7YYG-CUTOWR-SEALEV-HVTDFR-J54BQY-DKTI Remote Address on above: NCWUBA6DVLKE4EOQFM45CRJC255XHPMQHSPVM5PQ

Summary so far: Changing a general account to a Multisig account changes the Remote account. So far, it is the same as switching from NCC to NanoWallet.

The following example assumes a 2-of-3 multiside account. The problem is below.

1. In the general account, the Remote account is set to Active.
2. Change this general account to a multi-sig account.
3. From Signer, go to the setting item "Manage delegated account of Multisignature account".
4. Since the Remote account has been changed, try changing the Remote account. (In the case of NanoWallet from NCC, you can Deactivate the previous Remote account by using Custom Public Key.)
5. If you try to Deactivate Remote account before MultiSig using Remote account using Custom Publickey, an error occurs. 'FAILIRE_TRANSACTION_NOT_ALLOWD_FOR_REMOTE'
6. Conversely, for a newly created Remote account that is not Active, accepting deactivation of Remote Account will be accepted???, but if you use a signature from AndroidWallet, the program abnormally ends. (Android Wallet plays the role of a signatory properly when remitting money.)

To solve the problem, you need to deactivate the Multisig account once. It is very troublesome work. I do not know the reason why Custom Public Key can not be used.

I also tested it in another Multisig group. There is reproducibility.

Thanks

BugBoundary Address: NCVGXT-CV7YYG-CUTOWR-SEALEV-HVTDFR-J54BQY-DKTI

[mizunashi]

After all, in the case of Multisig it seems to be complicated due to the issue of authority. It is necessary to operate once after canceling multi-sing once.