When I post a statistic greater than 2,147,483,647 the statistic is not updated. (This is logical as its greater than int32.max) However after this happens when the same client posts another statistic that is smaller, it still does not get updated. The client has to restart. Is this the desired behavior or a bug?
I did some testing of this in my own title. First of all, when attempting to update a statistic with a value that exceeds int32.max I get back a 400 http response with an InvalidParams error. That's about what I would expect. If I then use a smaller value, I get back the expected 200 response.
When you say it fails silently, where are you looking? You mention loglevel.all. Is that something specific to your game engine? When you're unable to make subsequent updates after the first failure. Is it possible you're doing some sort of client side caching and retying failed requests?
Overall, the service appears to be workgin as expected, so I'm trying to understand what is unique about your scenario.
Hi, thanks for a quick turnaround.
I meant the PlayfabSettings.LogLevel in the Unity SDK
Did I misunderstood what this does?
Sending such a large number was a problem on my part, and after correcting that all is good.
The weird behavior was that subsequent requests did not update the statistic. I am not caching requests myself. I am using the Unity SDK, does this do so?
It looks like you've stumbled upon a piece of the Unity SDK that's a bit out of date. PlayFabSettings.LogLevel isn't used anymore. Setting it doesn't change any behavior. If you want to understand the errors your PlayFab API calls are encountering, you have to include an errorCallback Action in the method call.
2 People are following this question.