New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v1.19.2 doesn't use latest API version #1143
Comments
+1 |
Can someone from Stripe answer? |
I was experiencing the same issue. I managed to resolve this issue by updating my API version in the Stripe Dashboard. Go to dashboard > Developers > Overview tab - Scroll to the bottom and find API version. Change it the latest version and then retest. |
what about test mode? |
Hey all! There's a couple things to unpack here, I'll probably give too much info in case it's useful. There are a few potential ways versions can be set (and exist) within Stripe:
The CLI tries to be as version-agnostic as possible to support different users' integrations:
In this case, when you run the Upgrading your account's API version could help since that would change the default version the CLI is using too (after 24 hours) but that can only be done in livemode as well and is a large effort you'd have to undertake (I would not recommend doing the upgrade via the dashboard for the problem here). |
Add --latest solved my issue in Test mode as @tomer-stripe mentioned |
The C# stripe.net package (a 2023-08-16 version) only accepts the 2023 version when processing a webhook. Is this an issue with the library or the stripe CLI. Is stripe.net supposed to be backwards compatible? |
Issue
When running
stripe trigger checkout.session.completed
targeting a .NET project using Stripe.net v43.11.0, I get the error:when calling
EventUtility.ConstructEvent(json, req.Headers.GetValues("Stripe-Signature").FirstOrDefault(), _stripeEndpointSecret);
Expected Behavior
Successful validation of header
Steps to reproduce
stripe trigger checkout.session.completed
to the .NET projectTraceback
Environment
.NET 8.0
The text was updated successfully, but these errors were encountered: