Skip to content
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

paypal sometimes broken since 3.96.0 #691

Closed
719media opened this issue Aug 3, 2023 · 4 comments
Closed

paypal sometimes broken since 3.96.0 #691

719media opened this issue Aug 3, 2023 · 4 comments

Comments

@719media
Copy link

719media commented Aug 3, 2023

General information

  • SDK version: 3.96.1
  • Environment: Sandbox + Production
  • Browser and OS Any

Issue description

When using version 3.96.0+, occasionally the Paypal onShippingChange handler will not include paymentId in the paypal data, which is required for using https://braintree.github.io/braintree-web/current/PayPalCheckout.html#updatePayment (and other endpoints as well). I can't determine the scenario that produces this result on production, but on my development instance I can replicate it.

Basically renders the paypal widget useless as a customer can't update shipping/complete a payment without a paymentId. The manifestation of this bug for me is that every shipping address looks undeliverable from paypal's standpoint, as the callback I send back to braintree using the upddatePayment methods results in an error that the paymentId is missing. Looking into the paypal data argument provided to the from braintree to the client in the onShippingChange handler, I can see that paymentId is indeed null.

Please advise, in my opinion this is a fairly serious bug as it prevents checkout!

@jplukarski
Copy link
Contributor

Hey @719media, thanks for the report. I can reproduce this on my own test site. We'll take a look at this.

For internal tracking -> DTBTSDK-2902

@avisra
Copy link

avisra commented Aug 18, 2023

We are running into this issue too - our paypal transactions through braintree are failing

@jplukarski
Copy link
Contributor

@719media & @avisra , this issue has been resolved. Since the issue was in the PayPal backend, there shouldn't be a need to update the version.

Let us know if you are still running into any issues.

@jplukarski
Copy link
Contributor

This issue has been resolved. If this issue happens again feel free to re-open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants