-
-
Notifications
You must be signed in to change notification settings - Fork 730
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
[Stripe/active_merchant] Checkout error prevents order completion #9580
Comments
No, it confirms that the release introduced the bug because I didn't deploy to FR. |
This issue has been linked to an error in Bugsnag |
An error linked to this issue has been marked as fixed in Bugsnag |
https://github.com/openfoodfoundation/openfoodnetwork/releases/tag/v4.2.10 Comment added in Bugsnag by Maikel |
Looking at logs to see what actually blows up:
As seen on bugsnag (request):
|
Description
Probably introduced by #9507 and/or #9456.
Since the last release we're getting errors on some instances:
lib/active_merchant/billing/gateways/stripe_payment_intents_decorator.rb:60
UK
https://app.bugsnag.com/yaycode/openfoodnetwork-uk/errors/62fb43b59ffd5b0008478b23?filters[event.since]=all&filters[search][]=undefined&filters[search][]=method&filters[search][]=%60first%27&filters[search][]=for&filters[search][]=nil%3ANilClass
AU
https://app.bugsnag.com/yaycode/openfoodnetwork-aus/errors/62fc74ff173ec3000888a0ec?filters[event.since]=30d&filters[app.release_stage]=production
US
https://app.bugsnag.com/yaycode/openfoodnetwork-usa/errors/62fbeb745f03710008c2983d?filters[event.since]=30d&filters[error.status]=open
This is preventing checkout for some customers. The "Checkout failed" flash message is displayed.
Expected Behavior
Checkout succeeds and the credit card is saved in the profile.
Actual Behaviour
Error at checkout prevents completing the order.
Steps to Reproduce
Saving a new card during checkout:
Animated Gif/Screenshot
Workaround
Severity
Your Environment
Possible Fix
To be checked: The fact that it is so far not observed in FR could indicate that the bug affects only cards not requiring SCA?The text was updated successfully, but these errors were encountered: