I see both this: popularity 2.548249 and popularity "2.3815020000000002"

I've discovered what is causing this and the fix will be going out shortly. You'll have to wait the usual ~8 hours for the cached items to expire before you see it fixed everywhere.

Also... I remember that the popularity field could have values like 1234.56 but is it now changed to 1...10?

Nothing has changed here, it's still 0..infinity.

Thanks!

The problem still persists and it happens to all numeric fields. Should the fix already be live?

I don't see it happening in the links that @MarcoTC provided. What's an example URL?

It seems like things are improving, so it might just be a caching issue by now.

When loading this file: https://api.themoviedb.org/3/movie/10378?api_key=123&append_to_response=alternative_titles%2Ccredits%2Cexternal_ids%2Cimages%2Creleases&include_image_language=en%2Cen%2Cnull&language=en you even get "mixed" results. The aspect_ratio for posters is find, but for backdrops it still contains strings. All other numbers seem fine as well.

Ah yes, that would probably still return a string. We upgraded Ruby, and one of the changes they made in a newer version was to merge their Bignum and Fixnum classes into Integer. The JSON encoder seems to be getting confused now.

I'll look into this more today and report back once I figure it out.

The fix for this just went live. On any append to response call, the result should be showing the correct values. @jendrik Your query above is now returning proper floats for example.

Let me know if you see this anywhere else.

Looks like this has done the trick. All responses I have checked seem ok. If anything comes up again I will let you know.

Thanks for the quick fix!