Bug Float parameters in custom events dont work

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.

 

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

Code (CSharp):

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

And here is the configured event in the dashboard:



With 2 test samples the output is the following one:

Code (CSharp):

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

Code (CSharp):

1. SendEvent("tiempoSala", new Dictionary<string, object>() {
2.    { "tiempo", 0.4f },
3.    { "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

 

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

 

I am still facing this issue what is the solution for this....

 

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...