Is the Content Delivery API returning naive timestamps for anyone else?

[markadrake]

The documentation leads me to believe that the timestamp I'd get back looks like this:

  "name": "string",
  "createDate": "2023-06-23T11:31:07.281Z",
  "updateDate": "2023-06-23T11:31:07.281Z",

In version 13.6.0 of Umbraco, I receive this:

  "name": "Example",
  "createDate": "2025-02-03T15:29:01.237435",
  "updateDate": "2025-02-03T16:40:20.253199",

This is a problem because JavaScript treats this as a naive date and does not transform it to the visitor's time zone. I have to perform extra work on the client side to address this. I'm wondering if this was always the case if a recent update caused a change, or if something we've done has inadvertently impacted the API.

[nul800sebastiaan]

Looks good to me on v13

And v15

This place is more for posting feature requests, so I'll recommend you continue this either on the forum or Discord. And if you find steps to reproduce the problem, then it's a good one for the issue tracker.

[jdpnielsen]

I can reproduce the error after upgrading.

This is my umbraco cloud (development environment) v13.5.3:

This is my local environment v13.6.0:

[nul800sebastiaan]

Yikes, please report an issue so it can be looked at!

[nul800sebastiaan]

I just upgraded to 13.6.0 and I unfortunately don't get this problem, so we'll need some more reproduction steps, not sure what is happening.

[nul800sebastiaan]

Also tried the same, I had a 13.5.3 project on Cloud and updated it locally to 13.6.0 (also updated Umbraco.Forms.Deploy to 13.1.0, that was the only other available update for v13). No dice though, the dates are properly formatted.