Paypal-checkout-components: Refuse to get unsafe header "paypal-debug-id"

Created on 17 Aug 2017  路  13Comments  路  Source: paypal/paypal-checkout-components

Hi, every the paypal screen opens I get this error: can someone help ? Thanks !
image

outdated

Most helpful comment

Going to reopen this issue while I investigate. Thanks for the heads up.

All 13 comments

Thanks for the heads-up! Getting a fix out for this asap.

This should now be resolved, please clear your cache, make sure paypal.version === '4.0.112' and you should be good.

I am encountering this too. It always happens during paypal create payment when using php rest sdk under this code

            payment: function() {

                // Set up a url on your server to create the payment
                var CREATE_URL = '/demo/checkout/api/paypal/payment/create/';

                // Make a call to your server to set up the payment
                return paypal.request.post(CREATE_URL)
                    .then(function(res) {
                        return res.paymentID;
                    });
            },

image

Is there any progress on this one ? Same happens for me using the node rest sdk

image

Can you advise what paypal.version shows in your console? Thanks

Have same issue
screen shot 2017-10-13 at 22 14 00

Same issue with version 4.0.136:

unsafe-header-paypal

Going to reopen this issue while I investigate. Thanks for the heads up.

Hey all this is a CORS issue not a JS issue
The response from your payment URL needs the following header even if the header isn't being set Access-Control-Expose-Headers: paypal-debug-id
I can also see that this is wrapped in a try/catch in my version but still outputs an error in the console but doesn't stop execution

Thanks @oilee80

Do others on this thread actually see the flow being blocked by this error? Or do you just see the error in the console without any other effects?

@bluepnume no, flow wasn't blocked by this error, it was just red error in console, in my case, didn't affect anything I aware of.
But I don't see such error recently, it disappeared. Guess it was fixed, or you changed smth...
paypal.version is 4.0.157

Yep! This was fixed in the latest release.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Was this page helpful?
0 / 5 - 0 ratings