question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

There is no validation on wallet name while importing new wallets from *.json file

See original GitHub issue

Wallet version or commit SHA: design-v2 branch (b2519ef)

Environment: MacBook Pro (13-inch, 2017), macOS Mojave 10.14

Reproduction steps:

  1. Create a new wallet named “test”
  2. Login to newly created wallet
  3. Click on “Settings” button in the left menu
  4. Click on “Export” button and save *.json file anywhere
  5. Close your Neon wallet and clear it’s app data (fresh Neon wallet installation)
  6. Start Neon wallet
  7. Create a new wallet named “test”
  8. Login to newly created wallet
  9. Click on “Settings” button in the left menu
  10. Click on “Import” button and choose previously saved *.json file
  11. Logout from current wallet
  12. Click on drop-down with saved wallet => you can see 2x “test”, both of them will login you to the wallet which was created as 1st

Description: If you have a saved wallet named “test” and then you import a *.json file with another wallet which has exactly the same name (“test”) - you will end up having 2x “test” wallet in the app. You’re able to login only to first wallet created (saved wallet in this case), doesn’t matter which “test” wallet you’re going to choose from drop-down list (1st “test” or 2nd “test”) - it will always log you in to the 1st one.

Screenshots/Video: Video is taken from 6th reproduction step (after saving *.json file with a wallet named “test”): https://i.imgur.com/h3LEgkq.gifv

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
drptblcommented, Nov 20, 2018

@ranbena @evgenyboxer This seems to be partially solved. Currently (after recent changes), if you try to import a *.json file which contains a wallet with the same name as one of the saved wallets, you will get following error: wallet-exist

I think that it’s quite unclear in situation if you’re trying to import a file with more than 1 wallet (for example 5 wallets in *.json file). You will end up having no idea which wallet blocks the import. It would be good to show names of the wallets that are blocking the import, so user is aware which wallet names to change. What do you think?

0reactions
drptblcommented, Nov 27, 2018

Looks good now, thanks 👍.

Read more comments on GitHub >

github_iconTop Results From Across the Web

bitcoinlib.wallets module
Generate masterkey or import key when specified. When only a name is specified a legacy Wallet with a single masterkey is created with...
Read more >
"JSON data is not expected" when trying to import crypto ...
The error message "JSON data is not expected" pops up when the user is trying to import crypto wallets into Brave Wallet.
Read more >
How do I import an existing wallet? - AlphaWallet
How do I import an existing wallet? Click Settings, then click Change / Add Wallet, then click Add(on top right corner), then click...
Read more >
Wallet Developer Guide: Pass Design and Creation
At the center of the pass is a JSON file named pass.json , which ... In addition to the pass type identifier and...
Read more >
5. Transactions - Mastering Bitcoin [Book] - O'Reilly
In effect, there is no such thing as a stored balance of a bitcoin address or ... get unspent outputs from blockchain API...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found