Delegated Harvesting problem.

[tongokongo]

Before submitting your issue, please review the following checklist:

• [x] AVOID using the issue tracker for questions or help. Submitting issues to this repository are usually reserved for bugs, feature requests, or changes to the source code. If you need help https://forum.nem.io should be first place to visit.
• [x] DO describe operating system and browser used

Expected Behavior

Harvesting status should be uniform in the same account

Current Behavior

Opening Manage delegated account of multisignature accounts tab in chrome browser gives me delegated harvesting status active. Opening the same tab for the same account it gives me inactive. ^Mozilla Firefox, harvesting inactive ^chrome, harvesting active ^Multisig account, harvesting inactive ^Second cosigner account, harvesting inactive

Possible Solution

I don't know solution

Steps to Reproduce

1. Start delegated harvesting in cosignatory_1 account -> harvesting active
2. Log into cosignatory_1 account on another browser -> harvesting inactive
3. Or log into cosignatory_2 account or into multisig account -> harvesting inactive

Details

This may be connected, while trying to log off from the delegated harvesting (multisig) screen I am getting this error "Unknown wallet encryption record".

Then I got this information after logging off: "Provided password is not valid."

[mizunashi]

About the browser. In this case, the delegated harvesting server information saved by the browser side saved different information. So, the browser for remote harvesting is incorrectly recognized by the browser. Different results are displayed for this reason.

About harvesting under multi-sig environments (I did a test before) M accounts with funds. Suppose M is managing the multisig with C1 and C2.

Here, M has three management methods. Suppose that the remote account of M is valid before configuring multisig. After that, M sets up to perform multi-sig administration with C1 and C2. In this case, you can log in with M and control the harvesting request.

After actually creating the Multisig environment, you can activate Remote account of M and manage harvesting at C1. However, what to note here is that the Remote account is different in this way from the case of writing above.

This also applies to activating Remote account of M in C2 and managing harvesting. To my satisfaction, the Remote account used will be a separate account from C1.

There are three activation and management methods, and you need to recognize that they use different Remote accounts.

BR has a memory saying that it is better to manage with M.

Provided password I also see this well. (^_^;)

PostScript: My dream is to be featured in tongokongo's weekly news. lol