ERR_NAME_NOT_RESOLVED in sandbox

I don’t know if this is related to #1232 but it’s a similar error. When trying to load buttons on my checkout page in sandbox mode, Chrome’s console keeps showing an ERR_NAME_NOT_RESOLVED. Switching to a production client ID fixes this. It looks like tracking.qa.paypal.com is not resolving? I’m also not sure why this tracking is running as it looks like it’s for muse… but I could be misreading things.

Loading <script src="https://www.paypal.com/sdk/js?client-id={{ paypal_client_id }}&intent=authorize&disable-funding=credit,card"> works fine, but eventually tries to load

https://tracking.qa.paypal.com/webapps/tracking/ts?pgrp=muse%3Ageneric%3Aanalytics%3A%3Amerchant&page=muse%3Ageneric%3Aanalytics%3A%3Amerchant%3A%3A%3A&tsrce=tagmanagernodeweb&comp=tagmanagernodeweb&sub_component=analytics&s=ci&fltp=analytics-generic&pt=Checkout&dh=2560&dw=1440&bh=570&bw=1440&cd=24&sh=2560&sw=1440&v=NA&pl=pdf&rosetta_language=en-US%2Cen%2Cen-GB&e=im&t=1572990936618&g=480&completeurl=http%3A%2F%2Flocalhost%3A8000%2Fcheckout%2Fplaceorder%2F&sinfo=%7B%22partners%22%3A%7B%22ecwid%22%3A%7B%7D%2C%22bigCommerce%22%3A%7B%7D%2C%22shopify%22%3A%7B%7D%2C%22wix%22%3A%7B%7D%2C%22bigCartel%22%3A%7B%7D%7D%7D

And Chrome complains loudly.

Production uses https://t.paypal.com/ instead and that loads fine. This was also working about a month ago, I think. This fails in Firefox too, but does not throw a console error. I noticed this because I have a check in my Selenium tests to alert me about severe console errors (to catch something I did). I can still click the checkout button and I think things work as expected, it’s just a frustrating error to see every time.

[AlessandroGambaro]

If you are using euro, you need to:

1. https://www.paypal.com/sdk/js?currency=EUR&client-id=
2. purchase_units: [{ ‘intent’: ‘CAPTURE’, amount: { currency_code: ‘EUR’, value: in string value with two decimal } }]

[github-actions[bot]]

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.