Integration and Testing

[gabsiscoding]

We recently put our Accept.js implementation into production and have noticed through our NewRelic monitoring and tracking that a high number of generic script errors seem to be occuring when loading Accept.js in Chrome 44 on Android. 

From NewRelic I have the following information on this issue:

Message Exception type Approximate time URL Browser User agent

Script error.

UncaughtException

Yesterday, 17:15

/

Android Chrome 44

Mozilla/5.0 (Linux; Android 6.0.1; SAMSUNG SM-G550T1 Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/4.0 Chrome/44.0.2403.133 Mobile Safari/537.36

Stack trace

UncaughtException: Script error. in evaluated code

Here is another User Agent that also experiences this issue:

User agent

Mozilla/5.0 (Linux; Android 6.0.1; SAMSUNG SM-J700T Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/4.0 Chrome/44.0.2403.133 Mobile Safari/537.36

And a view of our user session events:

As this error halts the loading of our single page reactjs application, some help would be very much appreciated here!

[gabsiscoding]

Is it possible to get a reply from the Authorize.Net team on this issue?

[Aaron]

Hi @gabsiscoding,

We've released code in sandbox that fixes some Accept.js issues, and this code should make it into the production environment within the next couple of days.

Specifically for Accept.js, there's no longer any "Access-Control-Allow-Origin" related error in the console. I'm wondering if this error being generated client side is what was causing some clients to fail. Now that the error is not being generated at the client side, once that code reaches production can you continue to monitor your logs and see if anything improves or changes?