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

How to fix migration and cookie associated with a cross-site warnings with react-stripe-checkout #149

Open
performautodev opened this issue Apr 16, 2020 · 3 comments

Comments

@performautodev
Copy link

I want to use 'react-stripe-checkout' without warnings!

https://www.npmjs.com/package/react-stripe-checkout


i am take a look on the github repo i don't see any migration! wow! > https://github.com/azmenak/react-stripe-checkout
All is good but there are warnings how to fix it (PLEASE HELP ME) ? Those warnings are very ugly! it's kill me! :(
``` checkout.js:3 You’re using the legacy version of Stripe Checkout.

We released a new version of Checkout in April 2019, which supports mobile wallets and other payment methods:
https://stripe.com/docs/payments/checkout

Learn how to upgrade to the new version:
https://stripe.com/docs/payments/checkout/migration


A cookie associated with a cross-site resource at http://checkout.stripe.com/ was set without the SameSite attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with SameSite=None and Secure. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

My code is so simple:

<StripeCheckout
amount={999}
stripeKey="pk_test_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
token={res => this.onTokenCall(res, createOrderOnCall)}
>
{this.props.children}

@kckusal
Copy link

kckusal commented May 8, 2020

Yes, this needs attention, please.

@jmdmacapagal
Copy link

+1 on this

@pablogperez
Copy link

I wonder if this is getting maintenance, just to know if I will have to look for another option before it starts breaking because of that Chrome update.

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

4 participants