-
Notifications
You must be signed in to change notification settings - Fork 42
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
Importing Private Key asks for another Invitation code #984
Comments
|
Still happening in current version. |
Sorry for the inconvenience. Could you recheck the issue in the v100087 release? We have landed a fix for a similar case, and I'm guessing that fix should work on this case too. |
Still happening for users I'm afraid. We had 2 people mention it on discord and had to create new onboarding accounts to get invitation codes. |
Just for your information this is still happening in v97, almost everyday we have a few people having this issue. |
...A year past, and I just tested this and the result was,
...aand we also substituted MissingActivation view with just Activation view, but simply put this shouldn't be happening for already activated private key now. and I think we can close this issue. can I get a confirmation? |
#2114 Closes this issue. |
Hi Team,
When importing a private key instead of creating a new account. It asks for an invitation code to insert this existing private key into the launcher. The only workaround that exists for this is to create an extra account and hunt for another invitation code, which is not really great.
This can by bypassed if the user in question still has access to the 9c files on a previous PC or take a copy of their keyfile before formatting their PC. If you place the keyfile in the new installation (or new pc) then the launcher will read the data from the keyfile and won't ask for a new invitation code. So at this current time, using the keyfile as a recovery method is the only viable option that doesn't require creating a new twitter account and attempt to hunt for a new invitation code.
The text was updated successfully, but these errors were encountered: