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

Pre-login "point not owned" message is confusing #405

Open
Fang- opened this issue Mar 3, 2020 · 7 comments
Open

Pre-login "point not owned" message is confusing #405

Fang- opened this issue Mar 3, 2020 · 7 comments
Labels
copy needs attention from a writer feature things we should add, maybe interface shared

Comments

@Fang-
Copy link
Member

Fang- commented Mar 3, 2020

If the user attempts to log in with a ticket that doesn't own the ID they're trying to log in as/with, then they get dislayed a message.

// warn the user
if (noPermissions && !didWarn.current) {
didWarn.current = true;
return {
[WARNING]:
'This wallet is not the owner or transfer proxy for this point.',
};
}

This is intended to be informational, and the login button transforms to say "login anyway", but it seems (from support conversations) users often miss that cue. This looks and sounds like an error, so clicking login again (and so, even looking closely at it) isn't a natural follow-up action.

I don't remember what this message was supposed to buy us anymore. Maybe we should just remove it?

@Fang- Fang- changed the title Pre-login "no owned points" message is confusing Pre-login "point not owned" message is confusing Mar 3, 2020
@belisarius222
Copy link

This just happened to my friend, but he clicked the "Login Anyway" button and it said "No points to display. This wallet is not the owner or proxy for any points." I had just given him a planet from an invite card, we redeemed it on bridge, and he typed in the @p and master ticket from the downloaded image. I don't know why his ownership isn't registered.

@belisarius222
Copy link

Oh, I think we forgot to do the "verify your ticket" stage. Maybe that's related?

@belisarius222
Copy link

Well, now I'm trying to do that step and it says "Does not match master ticket." I don't know how to proceed from here.

@belisarius222
Copy link

Ok, I just tried to verify a second planet invite, and it failed the same way. Seems like these invites are bunk. I don't know why they would be; a couple months ago I gave some to some friends that worked just fine.

@vvisigoth
Copy link
Contributor

vvisigoth commented Mar 8, 2020 via email

@belisarius222
Copy link

belisarius222 commented Mar 8, 2020 via email

@Fang-
Copy link
Member Author

Fang- commented Mar 11, 2020

I had just given him a planet from an invite card, we redeemed it on bridge, and he typed in the @p and master ticket from the downloaded image.

Oh, I think we forgot to do the "verify your ticket" stage.

I certainly hope you did! If you made it all the way through the invite flow (ending with a redirect to the point overview page), and you an then not log in with the master ticket you downloaded & verified, that's a Big Bug and needs serious investigation.
(You do, in fact, need to make it all the way through to actually claim the invite. Just downloading some files isn't enough, changes need to be made on-chain.)

now I'm trying to do that step and it says "Does not match master ticket."

When inputting the master ticket from the files you downloaded? That's very strange. Is this consistently reproducible, across sessions? It seems to have been working for everyone, across browsers and everything, not sure what you're hitting. If you can repro this, would appreciate help investigating.

Seems like these invites are bunk.

If you can enter the invite flow (ie can see the planet name associated with the invite), it's not bunk, and any further issue is on the Bridge side.

@lukestiles lukestiles added copy needs attention from a writer feature things we should add, maybe shared labels Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
copy needs attention from a writer feature things we should add, maybe interface shared
Projects
None yet
Development

No branches or pull requests

5 participants