Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to save receiving addresses in desktop wallet #152

Open
achterhooker opened this issue Jan 23, 2019 · 2 comments
Open

Not able to save receiving addresses in desktop wallet #152

achterhooker opened this issue Jan 23, 2019 · 2 comments

Comments

@achterhooker
Copy link

Not able to save receiving addresses in the desktop wallet.

To reproduce:

  1. Start the Gulden Desktop wallet
  2. In the menu go to File > Receiving Addresses
  3. Press New to create a new receiving address
  4. In the popup you can enter the label field but the address field stays greyed out

Expected behaviour

You should be able to enter and save a receiving address here.

Actual behaviour

You can fill out the label field, but the address field stays greyed out. Therefor you cannot enter and save an address here. The only way out is pressing the Cancel button.

adres

Gulden Desktop version 2.1.0.3

Running on Windows 64 bit

Additional info:
Saving sending addresses which works the same does work. Issue only occurs when trying to save a receiving address.

@devlz303
Copy link
Contributor

devlz303 commented Feb 8, 2019

I don't think you are supposed to manually add a new receiving address, because receiving addresses are part of your wallet.

However right now the receiving address book is always empty so you should be able to add them by (A.) selecting them in the new address dialog or (B.) the receiving address book should be filled with all previously used receiving addresses (but this can be a long list).

@achterhooker
Copy link
Author

i agree. i couldn't find a reason why i would manually add a receiving address there myself but maybe some users do. If the option is there, it should work or the functionally should be clear to the end user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants