Clock.Provider not working in abp v9

[yopichy]

based on https://aspnetboilerplate.com/Pages/Documents/Timing, i set Clock.Provider = ClockProviders.Utc.
before upgrade in abp v7 (NET6), when API received payload "2024-01-01T00:00:00.000+07:00" in SomethingAppService will be auto convert to "2023-12-31 17:00:00" [kind=utc], but in v9 (NET8) still "2024-01-01 00:00:00" [kind=local]

[yopichy]

as additional info, this issue only happens on HTTP POST (kind = local). on HTTP GET it remains the same v7 (kind=utc).
Is there relationship with changes from newtonsoft to system.text.json #6679?

[ismcagdas]

@yopichy I couldn't reproduce this issue. Is it possible for you to prepare a solution which reproduces this problem ?

I downloaded a new template from https://aspnetboilerplate.com/Templates and created the app service below;

public interface ITestAppService : IApplicationService
{
    Task DoSomething(DoSomethingInput input);
}

public class DoSomethingInput
{
    public DateTime Date { get; set; }
}

public class TestAppService : Issue6928AppServiceBase, ITestAppService
{
    public Task DoSomething(DoSomethingInput input)
    {
        return Task.CompletedTask;
    }
}

Then, I send the request below;

Ahd this is the value I get;

[yopichy]

@ismcagdas in startup clock provider using utc?

[yopichy]

If using a new template, i cannot reproduce too. I'm upgrade from older version to v9

when POST param using like this, kind is correct UTC.
and i changed inside class back to local

Can you guess why this happened?

[ismcagdas]

Can you compare your Startup.cs with the new project's Startup.cs ? It might help.

[yopichy]

@ismcagdas I only saw a difference in the part where there was no .AddNewtonsoftJson in new template, is that the problem?
the problem only occurs using the POST method with parameter object/class