[Bug] Console flooded with cookie warnings on PayPal component rerender

[blagoySimandov]

Console flooded with cookie warnings on PayPal component rerender

Library used

react-paypal-js

Describe the Bug

When the PayPal React component rerenders, the console is flooded with warnings related to third-party cookies.

Minimal Reproduction

1. Implement PayPal React component in a React application
2. Trigger a rerender
3. Observe console for multiple cookie-related warnings

Actual Behavior

On each rerender of the PayPal component, the console displays multiple warnings about third-party cookies. The warnings state:

"Reading cookie in cross-site context will be blocked in future Chrome versions

Cookies with the SameSite=None; Secure and not Partitioned attributes that operate in cross-site contexts are third-party cookies. In future Chrome versions, reading third-party cookies will be blocked. This behavior protects user data from cross-site tracking."

Expected Behavior

The PayPal component should rerender without triggering any cookie warnings.

Environment

• Node.js/npm: [v21.3.0]
• Browser: Chrome [Version 127.0.6533.89 (Official Build) (64-bit)]
  

[harshjaiswalprgm]

Update the react-paypal-js library.
Review and adjust PayPal SDK configuration.
Ensure cookies are set with appropriate attributes.
Control component rerenders to avoid excessive warnings.
Suppress warnings temporarily if needed for development.

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[dafariski77]

bump

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information.