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

Registering a Sponsored Name Results in an Empty Profile and Inability to Log In #1767

Open
jehunter5811 opened this Issue Jan 2, 2019 · 8 comments

Comments

Projects
None yet
4 participants
@jehunter5811
Copy link
Contributor

jehunter5811 commented Jan 2, 2019

It appears as if the flip to the new year caused a new bug with the name registrar/browser? This just started yesterday as far as I can tell, but registering a new sponsored name will result in an empty profile and an inability to log into apps.

This has been verified by myself and Nick from Blockusign.

@hstove

This comment has been minimized.

Copy link
Contributor

hstove commented Jan 2, 2019

Can you elaborate a bit more on the issue here? I just created a new subdomain (successfully), then logged into Graphite, and its working fine for me. My localStorage in graphite looks normal.

@hstove

This comment has been minimized.

Copy link
Contributor

hstove commented Jan 2, 2019

I just did some testing:

  • broken on local browser w/ Brave
  • works on local browser w/ Chrome
  • works on hosted browser w/ Brave
@jehunter5811

This comment has been minimized.

Copy link
Contributor

jehunter5811 commented Jan 2, 2019

@hstove I just tried registering a subdomain id in Firefox and got this error:

screen shot 2019-01-02 at 8 37 23 am

Before that, it seemed I was able to register a subdomain name, but when looking at the localStorage object, the profile looked like this:

{"@type":"Person","@context":"http://schema.org"}

It was missing everything else. I tried the name registration again to confirm and that's when I got the registration error you see in that screenshot.

@markmhx markmhx added the bug label Jan 2, 2019

@markmhx

This comment has been minimized.

Copy link

markmhx commented Jan 4, 2019

Here's what I'm seeing in local storage for the profile property upon redirect back to the app after registering a new subdomain name:

screen shot 2019-01-04 at 15 52 51

@jehunter5811

This comment has been minimized.

Copy link
Contributor

jehunter5811 commented Jan 9, 2019

This appears to be working as expected now! Just tested with both a name registered through the default hub and one registered on a custom hub. Unless you all need to look into anything else, I think this can be closed.

@markmhx

This comment has been minimized.

Copy link

markmhx commented Jan 9, 2019

@jehunter5811 That's great! Please let us know if it arises again.

@markmhx markmhx closed this Jan 9, 2019

@markmhx

This comment has been minimized.

Copy link

markmhx commented Jan 11, 2019

I'm reopening this issue since @ntheile is reporting it again in Slack here: https://blockstack.slack.com/archives/C07TM0PSM/p1547180118137500

screen shot 2019-01-11 at 12 27 27

@markmhx markmhx reopened this Jan 11, 2019

@hstove

This comment has been minimized.

Copy link
Contributor

hstove commented Jan 11, 2019

I think I ran into Nick's issue last night as well, inadvertently. It appears that when you first sign up and are auth'ing into a multi-player app, we don't update the profile to include the apps object. It does work successfully the second time you auth.

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