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

Receiving ErrorCode: 99 even though user is signed in to bungie.net #8

Closed
blainefricks opened this issue Aug 6, 2015 · 8 comments
Closed
Assignees
Labels
Milestone

Comments

@blainefricks
Copy link
Owner

getBungieNetUserRequest() is returning the following data even when user is signed in to Bungie.net:

Object {
  ErrorCode: 99,
  ThrottleSeconds: 0,
  ErrorStatus: "WebAuthRequired",
  Message: "Please sign-in to continue.",
  MessageData: Object
}

May need to also provide the bungledid cookie in the cookie header.

Cookies

In general, if you use an HTTP stack that correctly handles the Set-Cookie header in responses, you should be good to go. In particular, we ask that you support the bungled and bungledid cookies. These help us with specific diagnostics tasks, and will come in handy if you ever need us to help you troubleshoot an issue on Bungie.net.

See issue #18 for progress.

@blainefricks blainefricks self-assigned this Aug 6, 2015
@blainefricks blainefricks added this to the 0.1 milestone Aug 6, 2015
@blainefricks
Copy link
Owner Author

Fixed: application doesn't work if user is connected to a VPN connection.

@blainefricks
Copy link
Owner Author

Reopened: still getting error even after terminating VPN connection.

@blainefricks blainefricks reopened this Aug 6, 2015
@blainefricks
Copy link
Owner Author

Solved: must wait a good 30 seconds after terminating a VPN connection in order for the Bungie platform to be reached.

@blainefricks
Copy link
Owner Author

this could be an issue on Bungie's side

@blainefricks blainefricks added 4p and removed 4p labels Aug 6, 2015
@blainefricks
Copy link
Owner Author

this could be due to my internet being slow at the moment, will investigate.

@blainefricks
Copy link
Owner Author

Still having this issue even with fast internet, i'm assuming its an issue with Bungie.net at the moment.

@blainefricks
Copy link
Owner Author

May need to also provide the bungledid cookie in the cookie header.

Cookies

In general, if you use an HTTP stack that correctly handles the Set-Cookie header in responses, you should be good to go. In particular, we ask that you support the bungled and bungledid cookies. These help us with specific diagnostics tasks, and will come in handy if you ever need us to help you troubleshoot an issue on Bungie.net.

See issue #18 for progress.

@blainefricks
Copy link
Owner Author

Fixed! This was caused by a typo on the x-csrf header. Was using x-crsf.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant