Merit Core generated mnemonic from failed import wallet for new wallet, causing new wallet cannot be exported

[AbrahamAriel]

Describe the issue

I had a Merit wallet created on my mobile phone. So I tried to import the wallet into the Core desktop application to get ready for mining once I get my invite. However, Merit Core refuses to import the wallet. It says, "Unable to import the wallet with the mnemonic given". Then the program just won't allow me to press the "Import" button no matter how many times I restart the program.

I gave up eventually and created another wallet instead without the whole data and re-download the blockchain snapshot. Biggest mistake of my journey to use Merit. This new wallet was cleared for invite but it had the mnemonic of the my other wallet that I was trying to import.

To make it simple, I wasted an invite and this wallet will not be usable anywhere else. I can't back it up, I can't import it on anywhere else.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

1. Use Merit Core
2. Import an existing wallet with mnemonic
3. Once failed, create a new wallet without deleted data folder.

Expected behaviour

Any progress done with import should be reverted, wallet should be cleaned up and generated a new wallet with new mnemonics.

Actual behaviour

Wallet is not renewed, not cleaned up and mnemonic used for importing somehow replaced the mnemonic for the new wallet or the new wallet is created with those mnemonics.

What version of merit-core are you using?

0.5.4.0-0900ca8, binary release.

Machine specs:

• OS: Windows 10 Home 64-bit
• CPU: Intel Core i9-7900X
• RAM: 16GB
• Disk size: 2TB
• Disk Type (HD/SDD): HD

Any extra information that might be useful in the debugging process.

I couldn't find any lines particularly interesting in this case from any of the debug.log produced. However, if you must need them, I will provide them in a separate links to online paste websites.

[mempko]

Have you tried again after being up to date with the latest blockchain? It's possible this issue was caused by the core client not done syncing.