Problem with PlayFab (SOLVED)

yep.

Have you guys reached out to PlayFab and asked on their support forums? -5 indicates RESULT_CONNRESET. I wonder if you perhaps could debug this using an https proxy and wireshark or something like that?

1 Like

I sent them an e-mail asking them to check up on these issues.

I’m implementing PlayFab in a project right now so may have more info if I see the issues too.

Thanks for the email, and hi all! For help using PlayFab, I’d recommend using our forums, since that’s what we actively monitor for questions.

For this issue, I’d say the problem is the extra “/” in the URL (making the URL invalid). So the call isn’t actually getting out to us at all, it looks like. @Pkeod: Any idea what would cause that in Defold?

2 Likes

I took a look at the code and the code making the HTTP request looks like this:

Note the above is for Corona, but more or less the same code applies for Defold in PlayFabHttps_Defold.lua which can be found inside the PlayFabClientSdk.zip here https://github.com/PlayFab/LuaSdk/tree/master/Defold. BTW Where is the source code for PlayFabHttps_Defold!?

And it’s called like this:

As you can see there’s one ‘/’ added in PlayFabHttps_LuaSec.lua and one in the beginning of each urlPath passed into the function itself.

I created a post on the PlayFab forum: https://community.playfab.com/questions/16287/issue-with-url-creation-in-the-luasdk.html

This has been resolved in the PlayFab SDK now:

Please give it a try and verify that it works.

hmm, https://github.com/PlayFab/LuaSdk/ Latest commit 8742d94 23 days ago

1 Like

It looks like a small change to fix this if you edit your local copy

1 Like

Ah, they’ve probably not yet released a new version with the fix included. Not sure about their release process but it might be delayed until after x-mas sometime.

Solved in 1.2.162

3 Likes