Float parameters in custom events dont work

Unity Services
,
1

Hi, I was using the new Analytics package and I realized after hours of debugging that floating numbers are not correctly serialized when sending custom events from Unity. I have rounded the float to int (without even changing the schema in the dashboard to be still a float) and it works perfectly. Just try to send a custom event with a float/double parameter, and Unity will tell you this:

Incorrect response, check your JSON for errors.
Events failed to upload (code 400) – will retry at next heartbeat.

2

Hi, can you share the code used to send the event here so we can investigate it? Thanks.

3

Sure, here you have the function that sends any custom event I have.

private static void SendEvent(string eventName, Dictionary<string, object> parameters)
    {
        Debug.Log($"Event name: {eventName}");
        foreach (var p in parameters) Debug.Log($"Event parameter: {p.Key} - {p.Value}");
        Events.CustomData(eventName, parameters);
        Events.Flush();
    }

And here is the configured event in the dashboard:

With 2 test samples the output is the following one:

SendEvent("tiempoSala", new Dictionary<string, object>() {
   { "tiempo", 1 },
   { "sala", currentScene }
});


SendEvent("tiempoSala", new Dictionary<string, object>() {
   { "tiempo", 0.4f },
   { "sala", currentScene }
});

4

More info: REST API works perfectly with floats, so it seems to be something internal to the event serialization in the SDK

5

Hey everyone,

Just to update you: we verified this is a bug with the SDK.
Our teams will pick this up with urgency and we’ll update you as and when there’s a change.

We’ll update you as appropriate and when there’s a solution for you.

6

Hi there,

Sorry for the delay on this one, I’ve had a look at this but was unable to reproduce it locally. Could you confirm whether this is still an issue? If so I’ll have to look a bit further.

My initial thought was that the system locale may be set to Spanish where it’s apparently conventional to use a comma for a decimal separator rather than a dot but when I tested this locally on macOS I was unable to reproduce this after setting my locale to Spain (internally we use StringBuilder to convert the Analytics data into Json, it appears to handle these kinds of locale discrepancies as expected at least).

Please let me know if this is still an issue for you with the latest Analytics package or if we can close this bug :slight_smile:

Greets,
Miley

7

Quick update, just saw a different report come in that confirmed my suspicion, I’ll be having a look at this bug today, should be easy enough to fix once I’m able to reproduce it :slight_smile:

1 Like
8

If it helps, I had the same problem (operating system in french if its a problem of parsing float with different culture) : all custom events containing a float parameter didnt appear in Event Browser neither in valid/invalid tab.

Once I cast the value as integer in game and changed the parameter type to integer, those events appeared in the Event Browser

9

Good news :), I was able to fix this issue this morning and it will be going out with the next release of Analytics. I don’t yet have any ETA on when it will be released but shouldn’t be too long I presume.

10

I am still facing this issue what is the solution for this…:roll_eyes:

8475551--1126541--robo.PNG.jpg
8475551--1126541--robo.PNG.jpg1920×871 351 KB

11

This bug is still present in Analytics 5.0 with Unity 2020.3.44. My localization is ES-es, and floats just don’t work; I wasted a full day thinking it was my mistake and reconfiguring events and parameters…