PayPal Community

ct21 · ‎Sep-14-2020

In our on page load we do this: window.onerror = jsErrorHandler; the error handler function is: function jsErrorHandler(msg, url, line, col, error) { StackTrace.fromError(error).then(function(stackframes) { var stringifiedStack = stackframes.map(function(sf) { return sf.toString(); }).join(' '); var s = url + " (line " + line; if (col) { // Some browsers do not give col and error arguments s = s + ", column " + col; } s = s + ") " + msg; if (error) { s = s + " " + error; } s = s + " Stack Trace: " + stringifiedStack; //v6.05 Some ad blockers block this PayPal call. On Firefox the failed call comes up to our // error handler (for some reason on Chrome it does not). This is not a real error on our // web site and PayPal will work even when this call is blocked. So we ignore this error - // we do not report it and we do not redirect the user to the JS error page. if (msg.indexOf("paypal.com/xoplatform/logger/api/logger") >= 0) { return; } // Redirect to our JS error page and pass details HTML window.location = "jserror.html?details=" + encodeURIComponent(s); // Report this error to the server for logging and notification. // There is no data returned by the server, and we ignore any // failure in the call. // Gather as much info about the JS environment as possible. We don't display // this on the JS error page but do log this in the server. s = s + " Website version: "+VERSION; //v6.06 s = s + " Client Details "; s = s + " userAgent:" + navigator.userAgent; s = s + " appCodeName: "+navigator.appCodeName; s = s + " appName: "+navigator.appName; s = s + " appVersion" + navigator.appVersion; s = s + " platform: " + navigator.platform; s = s + " prototype:" + navigator.prototype; s = s + " URL: " + window.location.href; util.reportJSError(s); // Post JS error to our server }); return true; // In older IE versions, returning true supresses error dialog } Hope that helps!

ct21 · ‎Aug-13-2020

After months of head-scratching, a customer having the problem offered to help track it down. Turns out to be an ad blocker ("adblocker plus"). When configured with the "Block additional tracking" option it blocks the PayPal logger API (and several other PayPal calls). On Firefox the failed logger call shows up as an error in our global Javascript error handler (where we send it to the server for analysis and website support notification) and we redirect the user to an "opps, we had an error" page. On Chrome it never comes to our error handler. Even with these blocked PayPal calls, PayPal express checkout buttons work fine. Our solution was to look for this specific error and just ignore it: function jsErrorHandler(msg, url, line, col, error) { StackTrace.fromError(error).then(function(stackframes) { if (msg.indexOf("paypal.com/xoplatform/logger/api/logger") >= 0) { return; } window.location = "jserror.html?details=..." //...report this JS error to our server... } }

ct21 · ‎Aug-13-2020

For anyone else that comes across this... after months of head-scratching, a customer having the problem finally offered to help track it down. Turns out that an ad blocker ("adblocker plus") when configured with the "Block additional tracking" setting will block the PayPal logger API (and several others... complete block list is at https://easylist-downloads.adblockplus.org/easyprivacy.txt). For some reason the error from the blocked call bubbles up to our global JS error handler on Firefox. On Chrome we do not get this error in our handler (but I verified the call is blocked on Chrome). The solution for us was to specifically look for this error in our handler, and just ignore it (instead of re-directing the user to our "opps, we had an error" page). function jsErrorHandler(msg, url, line, col, error) { StackTrace.fromError(error).then(function(stackframes) { if (msg.indexOf("paypal.com/xoplatform/logger/api/logger") >= 0) { return; // Ignore this error } window.location = "jserror.html?details=..." // Redirect user to our error page //...report this JS error to our server... } }

ct21 · ‎Jun-26-2020

Our client side Javascript catches all uncaught errors and reports them back to our server where they are logged. We have seen a growing number of errors on Firefox 77.0 browsers lately in the PayPal SDK Javascript code (Windows and Linux systems). We capture the following details: The following Javascript error was reported to the web server on Fri Jun 26 08:50:08 EDT 2020: Error location:https://www.paypal.com/sdk/js?client-id=****&currency=USD&disable-funding=credit (line 2, column 47550) Error: Request to post https://www.paypal.com/xoplatform/logger/api/logger failed: [object ProgressEvent]. Stack Trace: ht/ Client Details: userAgent:Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:77.0) Gecko/20100101 Firefox/77.0 appCodeName: Mozilla appName: Netscape appVersion5.0 (Windows) platform: Win32 prototype:undefined URL: https://cabintechglobal.com/mn3007 The stack trace is not very useful, other than showing it happens in the ht() method where it detects a POST failure and throws and exception (which apparently is not caught anywhere and ends up on our error handler): function ht(n) { return function (n) { var ...; return new E((function (n, t) { ... var v = new c.XMLHttpRequest; for (var b in v.addEventListener("load", (function () { ... }), !1), v.addEventListener("error", (function (n) { ----> t(new Error("Request to " + r.toLowerCase() + " " + e + " failed: " + n.toString() + ".")) }), !1), v.open(r, e, !0), o) o.hasOwnProperty(b) && v.setRequestHeader(b, o[b]); a ? s = JSON.stringify(a) : u && (s = Object.keys(u).map((function (n) { return encodeURIComponent(n) + "=" + (u ? encodeURIComponent(u[n]) : "") })).join("&")), v.timeout = f, v.ontimeout = function () { t(new Error("Request to " + r.toLowerCase() + " " + e + " has timed out")) }, v.send(s) })) }({ ... }).then(hn) } We cannot tell when this is happening (page load, PayPal button click, payment attempt, payment complete) and have been unable to reproduce it ourselves, but we are concerned that some customers are unable to complete orders on our website because of this. How can we find out what is going on and fix it?

ct21 · ‎Jan-22-2018

Do you know where USPS has documented this change in the international package rates? The only official info I can find is just the usual rate adjustments, I don't find any official USPS statement about this reclassification. If you are correct, this is a huge impact to many companies that ship international. We commonly ship 2oz padded envelopes for about $3.50 to most any country. Now we are looking at over $10 for the same shipment, about a 300% increase. This will destroy our international sales.

ct21 · ‎Jan-21-2018

Starting today we cannot print international labels - domestic US labels print fine. New USPS rates took effect today - not a coincidence I imagine. This has disabled my business since we cannot print first class labels on the USPS site (not to mention the hassle of copy/pasting each field of the address for every shipment). Not the first time PayPal has stopped my business dead in its track due to its flawed software.

ct21 · ‎Nov-29-2017

Please don't tell me webhooks only work for REST-submitted payments?? I have been totally operating on the assumption any time a payment is made to my account by any method (e.g. customer purcahse on Ebay, customer purchase on our web site shopping cart, customer payment of an invoice...) the webhooks would be called. What use would they be otherwise??

ct21 · ‎Nov-29-2017

I went through all the steps to create an application and webhooks. I tested with the simulator and it worked as expected. I created the webhook in the Live system for all event types. I am getting no calls to my server and no events show in the dashboard (https://developer.paypal.com/developer/dashboard/webhooks/live). E.g. I logon to paypal and create an invoice. That should generate some events. A customer makes a purchase on Ebay, that should generate some events. But my endpoint is not being called, and the dashboard shows zero events for the last month. help! -thanks

ct21 · ‎Nov-16-2017

I get an email notification from PayPal when a customer makes a payment (via Ebay or the shopping cart on our web site). It is the usual "You received a payment of...". In that email is a link to the transaction. Clicking on that link should take me directly to the transaction details (after login if needed). But lately these links are not working and instead take me to the PayPal Summary page. It is a major hassel to then try to find the transaction that corresponds to the email I am looking at. It used to be that only once in a while would a transaction link not work, now it is almost every email I get. Anyone else having this problem, any known solutions? Thanks!

ct21 · ‎Aug-11-2017

Yesterday we started getting customer complaints that when they try to pay with PayPal they get the infamous: Things don't appear to be working at the moment. Please try again later. I have looked at our POST request and I don't see anything wrong, here are the form fields as reported by Chrome Developer Tools: cmd:_cart upload:1 currency_code:USD business:admin@cabintechglobal.com rm:2 tax_cart:0.00 handling_cart:0.00 charset:utf-8 return:http://www.cabintechglobal.com/order_success.html cancel_return:http://www.cabintechglobal.com/ item_name_1:Xvive MN3005 4096-Stage Analog Delay Line (DIL-8 special) quantity_1:1 amount_1:18.50 item_number_1:1 option_index_0:0 item_name_2:Shipping Service: USPS First Class Mail $2.67 (United States (Domestic and APO/FPO/DPO Mail)) quantity_2:1 amount_2:2.67 item_number_2:2 option_index_1:0

PayPal Community

Re: Getting many Javascript errors on Firefox 77.0

Re: Getting many Javascript errors on Firefox 77.0

Re: Getting many Javascript errors on Firefox 77.0

Getting many Javascript errors on Firefox 77.0

Re: Can't print international labels using "ship n...

Re: Can't print international labels using "ship n...

Re: Webhooks for invoices created through PayPal d...

Webhooks not being called, not showing in dashboar...

Instant payment email transaction links don't work...

Our shopping cart stated failing yesterday... cann...