#henning-reimers_api

1 messages · Page 1 of 1 (latest)

glossy turretBOT
#

👋 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/1438130448441278494

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

uncut gazelle
edgy hazel
#

hey there 👋 could you clarify what about the last_seen_at value seems to be incorrectly formatted, or where you're seeing an error that indicates this?

uncut gazelle
#

it seems to be in milliseconds and your SDK cant handle that

#

Its not my code that is crashing, its the SDK. This is the code i use and at the second line, it is crashing:

var service = new Stripe.Terminal.ReaderService();
var readers = service.List(new Stripe.Terminal.ReaderListOptions { Limit = 100 }, requestOptions);

#

I first thought its maybe because i have a very old simulator device in my reader list, but my clients also have the same problem and they only have one or multiple real terminal devices.

#

And that is happening since i have updated the SDK from 2022-08-01 to 2025-10-29 a couple of days ago.

edgy hazel
#

thanks for your patience, taking a look with my team at the moment

glossy turretBOT
lilac atlas
#

Hey! Taking over for my colleague. Let me catch up.

#

I'm not able to reproduce the issue you are facing using the following code:

Stripe.apiKey = "YOUR_STRIPE_SECRET_KEY";
Reader debugReader = Reader.retrieve("YOUR_READER_ID");

I'm testing the latest SDK version 30.2.0

uncut gazelle
#

This is my Code:

StripeConfiguration.ApiKey = apiKey;
var requestOptions = new Stripe.RequestOptions
{
StripeAccount = this.ACCESSDATA.STRIPE_USER_ID
};
var service = new Stripe.Terminal.ReaderService();
var readers = service.List(new Stripe.Terminal.ReaderListOptions { Limit = 100 }, requestOptions);

Maybe its because of the Connect Client?

#

Iam using 49.2.0 as SDK version

#

(its .Net)

lilac atlas
#

Ah sorry, doing a test with .NET then

#

Ok, it seems like there is an issue with the DotNet SDK

uncut gazelle
#

How long will it take to fix? I’m just asking whether it makes sense to rewrite my functions to use the REST API instead of the SDK for the reader calls.

lilac atlas
#

I'll raise this with the owning team, but I can't garantee a resolution time, sorry.

uncut gazelle
#

Days, weeks or maybe months?

lilac atlas
#

May I ask you to write in via the DM you'll receive ? The support case will come to our team directly. So that we can notify you whne this is fixed

uncut gazelle
#

Sure

lilac atlas
glossy turretBOT
#

Hello @uncut gazelle, we have sent you a direct message, please check it at https://discord.com/channels/@me/1438141849629098085

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
uncut gazelle
#

ok, thanks