Frontend sends hello to backend, then chokes on response #526
Comments
|
Oh. Turns out that yes, this is an error that appears, but it’s simply ignored and does not keep MTGATracker from working. I simply did not know that I had to enable detailed logging. To be fair, it’s not mentioned anywhere in the readme. So, I’m now able to use MTGATracker, but I’ll still leave this issue open because maybe you want to update the readme and/or get rid of that misleading error message. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I’m new to MTGATracker and I’ve installed 6.1.0, started it up, and the window is pretty empty (only the “Total” and “Total: Session” rows are displayed). Editing decks and playing matches doesn’t change that.
I’ve put it into debug mode and I can see that during startup, some JSON parsing fails:
Looking more into it by clicking on
VM330:1on the right, I can see that the WebSocket message received isack hello!, which of course isn’t valid JSON (because it doesn’t start with curly braces or a double quote or something like that):mainRenderer.js:740mainRenderer.js:981hello!back verbatim:mtgatracker_backend.py:82I don’t quite understand why I should be the only one having this issue, it should affect everybody 🤔 Also, these lines haven’t been modified for a long time. So I guess I’m doing something wrong? If so, what? And what can I do to fix it?
The text was updated successfully, but these errors were encountered: