Page MenuHomePhabricator

Uncaught ERROR: One or more securedFields has just loaded new content. This should never happen (but it did, 10 times)
Closed, DeclinedPublic

Description

Another one in client-side errors that I noticed today. Looks like it's happened a handful of times. Again, this might be in the Adyen JS and not actually our error.

Nov 28 19:17:17 payments1006 adyen_gateway: 197808022:197808022.1
Client side error:
Array (

[message] => Uncaught ERROR: One or more securedFields has just loaded new content. This should never happen. securedFields have been removed. iframe load count=4. Expected count:3
[file] => https://checkoutshopper-live.adyen.com/checkoutshopper/sdk/5.39.0/adyen.js
[line] => 1
[col] => 304434
[userAgent] => Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Edg/119.0.0.0
[stack] => ERROR: One or more securedFields has just loaded new content. This should never happen. securedFields have been removed. iframe load count=4. Expected count:3
    at r.onIframeLoadedCallback (https://checkoutshopper-live.adyen.com/checkoutshopper/sdk/5.39.0/adyen.js:1:304465)
    at r.value (https://checkoutshopper-live.adyen.com/checkoutshopper/sdk/5.39.0/adyen.js:1:295691)
[donationData] => Array
    (
        [amount] => 1040.00
        [appeal] => JimmyQuote
        [email] => 
        [country] => US
        [payment_method] => cc
        [payment_submethod] => 
        [order_id] => 197808022.1
        [referrer] => en.wikipedia.org/
        [utm_source] => B2324_112817_en6C_dsk_p1_lg_txt_104.no-LP.cc
        [utm_medium] => sitenotice
        [utm_campaign] => C2324_en6C_dsk_FR_1128
        [utm_key] => otherAmt_1~changedAmt_1~ptf_1~vw_1912~vh_932~time_47
        [language] => en
        [action] => logPaymentsFormError
        [gateway] => adyen
        [recurring] => 
        [user_ip] => ***
        [server_ip] => 127.0.0.1
        [contribution_tracking_id] => 197808022
        [currency] => USD
    )

)

Event Timeline

I scanned across our code to see if this is something we added, and I don't think it is. However, it turns out that there are lots of things that "should never happen" across our code and libraries :)

image.png (932×1 px, 252 KB)

Confirmed that the error text is about a third of the way down the big blob of JS loaded from https://checkoutshopper-live.adyen.com/checkoutshopper/sdk/5.39.0/adyen.js

I think this is an Adyen-side bug. We just catch and log it because we're catching all JS errors on the page. We could try updating to a newer checkout JS version and see if it recurs.