-
Notifications
You must be signed in to change notification settings - Fork 14
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
"Received malformed payload" on match_data_send when upgrading to V3 #59
Comments
Are you testing with the code on The 3.0.3 version does not contain the fix for this issue |
I'm testing the latest release, that explains it then, thanks. |
I've requested a new release which includes the fix. |
That's great, thank you! I can confirm both my project and the example project work by using the |
I also had such a problem on the release, now I have a message sent on the master, but it does not go further
print("sended") - is not running |
@ufgo which version of the Nakama client are you using? The fact that you don't see the print() indicates that something crashes in the coroutine, but for some reason the error is not shown (I'll look into this)- |
Ah, logging is silent by default. Enable logging by doing this:
|
i use log. Nothing print about my problem |
Can you share a minimal repro case so that I can take a look? |
Closing due to inactivity. I was also not able to repro any problem myself. |
I seem to have this problem as well. tho. I raised my own issue #80 |
Hello, I followed the Defold+Nakama tutorial and created a similar game, then tried to upgrade the libraries to V3 and started getting errors on the server with "Received malformed payload".
I had some differences in code and setup so I continued my testing on the xoxo sample project branch and got the same results. Tried with multiple versions of the Nakama server and same thing.
Here's the decoded payload the server was complaining about:
When going back to
main
and enablingdebug
level on the server but I could only find this message:There are some visible differences:
match_data_send
vsMatchDataSend
Not sure if they should match one to one though, could be a red herring.
The text was updated successfully, but these errors were encountered: