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

Uncaught Error: Unable to retrieve keypair #2055

Closed
q9f opened this issue Dec 15, 2019 · 4 comments · Fixed by #2111
Closed

Uncaught Error: Unable to retrieve keypair #2055

q9f opened this issue Dec 15, 2019 · 4 comments · Fixed by #2111

Comments

@q9f
Copy link

q9f commented Dec 15, 2019

react.62389b3d.js:17 Uncaught Error: Unable to retrieve keypair '0xC...'
    at t.default (main.69fe13ec.js:21)
    at t.default.get (main.69fe13ec.js:88)
    at t.default.getPair (main.69fe13ec.js:88)
    at m.getPair (main.69fe13ec.js:88)
    at x (main.69fe13ec.js:100)
    at S.renderUnlock (main.69fe13ec.js:100)
    at S.renderContent (main.69fe13ec.js:100)
    at S.render (main.69fe13ec.js:100)
    at Ji (react.62389b3d.js:17)
    at Zi (react.62389b3d.js:17)

steps to reproduce:

  • have distinct controller 0xC and stash 0x5
  • bond funds for 0x5 and start validating.
  • forget the controller account 0xC
  • go the staking actions and try to change any settings for the validator 0x5
  • white page of doom
@jacogr
Copy link
Member

jacogr commented Dec 15, 2019

Yes, it currently does not try to see if you actually have the account before trying to use it. (The reverse is slightly better, i.e. having the controller and not the stash. As it blatantly obvious here, was was done assuming you have everything.)

@q9f
Copy link
Author

q9f commented Dec 15, 2019

yeah, it's an edge case. i agree usually, you should have the controller but not the stash.

@jacogr
Copy link
Member

jacogr commented Dec 15, 2019

Still needs a fix :) Thanks for reporting, the holes need to be closed.

@polkadot-js-bot
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Jun 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants