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

Better error handling for weird Bungie.net auth responses (no auth loops) #2058

Merged
merged 1 commit into from
Aug 4, 2017

Conversation

bhollis
Copy link
Contributor

@bhollis bhollis commented Aug 3, 2017

This should help us with "auth loops" when either Bungie.net or the user's browser is misbehaving. Instead of sending them directly back to the login page on missing code or state parameter, we'll display an error instead. It's not a very helpful error, but they'll at least have something to tell us.

Copy link
Member

@kyleshay kyleshay left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! Is there anything we could do to help the user know how to fix the issue? Goose mentioned clearing the cache or something similar to fix?

Should consider eventually pulling out the strings for i18n /cc @delphiactual

@bhollis
Copy link
Contributor Author

bhollis commented Aug 3, 2017

Hard reload is the same as clearing the cache, so we're good there.

Right now the auth return "app" doesn't have i18n set up at all.

@bhollis bhollis merged commit 0079eb0 into DestinyItemManager:master Aug 4, 2017
@bhollis bhollis deleted the authloops branch October 6, 2018 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants