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

Stuck on callback page #106

Closed
merelinguist opened this issue Aug 2, 2018 · 8 comments · Fixed by #232
Closed

Stuck on callback page #106

merelinguist opened this issue Aug 2, 2018 · 8 comments · Fixed by #232
Assignees
Labels
bug Something isn't working

Comments

@merelinguist
Copy link

Recently made my first Gatsby PR and trying to use the login button, but I don’t get redirected past the callback page.

@jlengstorf
Copy link
Contributor

Hey, Dylan! Are you seeing any errors in the console? What browser are you using? We've seen some weirdness with Safari (#93 should fix this), so if that's what you're using maybe give another browser a shot until we have the chance to patch that up.

Thanks!

@jlengstorf jlengstorf self-assigned this Aug 2, 2018
@jlengstorf jlengstorf added the bug Something isn't working label Aug 2, 2018
@merelinguist
Copy link
Author

Hey. I’m using Firefox on iOS (also tried Safari). I actually can’t get to a desktop until next week, but I’ll try again there and update you :). Thanks!

@jlengstorf
Copy link
Contributor

Sorry about that! I'll see if I can clear some time to fix the Safari issue sooner. (I think it has to do with the localStorage usage, which I think is weird on iOS.)

@merelinguist
Copy link
Author

Awesome 😎!

@stlk
Copy link

stlk commented Aug 11, 2018

I stumbled upon this issue too on Safari 11.1.2 (13605.3.8). It works fine on Firefox 61.0.1. Warning gets printed into console:

The resource https://store.gatsbyjs.org/static/d/696/path---callback-01-b-23e-NZuapzHg3X9TaN1iIixfv1W23E.json was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.

Not sure if I read the signs correctly but it looks like Auth0 client library returns null.

screen shot 2018-08-11 at 07 50 56

@jlengstorf
Copy link
Contributor

Thanks, @stlk! This definitely seems like something that Safari doesn't like about our code.

@lukeoliff a while back you had mentioned opening a PR to close #93 — I believe that would address this as well. Have you had the chance to look into this?

@Manoz
Copy link

Manoz commented Aug 22, 2018

Have the same issue on Chrome iOS. Looks like the website recognizes me but does not redirect me.

If I go back I’m not logged in even after refreshing the page.

http://imgur.com/rRL86C2

@jedrichards
Copy link

jedrichards commented Dec 6, 2018

@jlengstorf @Manoz Safari is not tolerant of hashes on urls that don't have a trailing slash. So something to check is that your AUTH0_CALLBACK url has a trailing slash on it ...

https://community.auth0.com/t/hash-gets-lost-on-safari-webkit-browsers/7263/6

jlengstorf added a commit that referenced this issue Jan 11, 2019
- Safari apparently requires trailing slashes or it dumps all hashes. So... we added a trailing slash.

closes #106
jlengstorf added a commit that referenced this issue Jan 11, 2019
- Safari apparently requires trailing slashes or it dumps all hashes. So... we added a trailing slash.

closes #106
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants