#fld00d_api
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1308878317910491237
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
Interesting... yeah I would expect that to be returned in seconds instead of ms here.
Give me a few minutes to look
Much appreciated!
@jade atlas is the issue just that your code is expecting it to be in seconds and thus you aren't decoding correctly?
It's actually in RequestService.cs on your NuGet package
public virtual Task<Request> CreateAsync(RequestCreateOptions options, RequestOptions requestOptions = null, CancellationToken cancellationToken = default)
{
return this.RequestAsync<Request>(BaseAddress.Api, HttpMethod.Post, $"/v1/forwarding/requests", options, requestOptions, cancellationToken);
}
Ah the SDK is erroring due to this?
yeah, let me grab the stack trace for you after decompilign the dll
That'd be great, thanks.
private T ProcessResponse<T>(StripeResponse response, ApiMode apiMode)
where T : IStripeEntity
Inside of LiveApiRequestor.cs is where the error is thrown, specifically this line
obj = StripeEntity.FromJson<T>(response.Content, this.jsonSerializerSettings);
Here's the stack trace
Okay got it.
I'll file a bug report internally and request that we get this fixed up here.
Oh good news, this has already been reported and is in the works already in terms of a fix: https://github.com/stripe/stripe-dotnet/issues/3028
I assume that report wasn't from you, correct?
correct, wasn't me...I had searched but failed to see it, guess I used the wrong key words, sorry about that
No problem at all
Appreciate you reporting it here
But also glad that a fix is already underway
Are we allowed to offer PR's against the main branch to expedite a fix, or is this 100% maintained internally?
You can submit a PR: https://github.com/stripe/stripe-dotnet?tab=readme-ov-file#development
thanks! I'll do that and then I'll be unblocked to test