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.

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

Invalid JSON Response #3

Open
wrighty43 opened this issue Apr 23, 2019 · 2 comments
Open

Invalid JSON Response #3

wrighty43 opened this issue Apr 23, 2019 · 2 comments

Comments

@wrighty43
Copy link

I have just tried this project again for a demo, but the JSON response seems to now be invalid. I presume something has changed on the server.
image
@wrighty43
Copy link
Author

It appears that this is from a token timeout. Deleting the old login token and regenerating fixes the issue, so some error handling needs to be inserted to avoid the crash and instigate a new token to be generated.

@mattwelch
Copy link
Contributor

Thanks for the report. It's an interesting error, as it seems like it's a JSON deserialization problem. The server handles non-JSON responses from the Sonos endpoint, and should always return JSON to the client. I'm trying to recreate, but have not been successful.

If you can get it to fail again, could you log the response from the server?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mattwelch @wrighty43