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.

Sign up for GitHub

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

Jump to bottom

Session-server bad request 400 #139

Closed

1 of 2 tasks

InhouseMedia opened this issue Jun 24, 2020 · 1 comment

InhouseMedia commented Jun 24, 2020 •

edited

Loading

Steps to reproduce:

session-server resturns 400 bad request on production apis

What should happen:

return a token

What happens:

Without changing code or deleting api keys the api stopped working.

The api key is registered within the Bunq App, but after that is crashes.

Created a new api key within the new V3 app, but also that didn't work.

Traceback

SDK version and environment

Tested on 1.13.0
Sandbox
Production

Response id

Response id: 361db673-42d3-4f67-a9c2-86bcf71f137e

Extra info:

InhouseMedia closed this as completed

Author

InhouseMedia commented Jun 29, 2020

My account at Bunq was corrupted. They fixed this issue.

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