Version Update causes JavaScript verifyBuyer Error

  • Resolved lbourgeois90

    (@lbourgeois90)


    2 years, 2 months ago

    I recently updated the WooCommerce Square plugin in my staging environment from version 4.0 to the newest version, 4.4.0. I have my staging environment set to run against my Square Sandbox. Since this update, credit card payment processing is failing on the VerifyBuyer step of payment processing unless I select the Securely Save to My Account option on checkout, then the transaction goes through successfully. My current version, 4.0, works fine when leveraging the Square Sandbox Payments. I have tried using the basic Storefront theme and the issue persists. Other payment methods that I am leveraging (PayPal and TeraWallet) all work as expected.

    Below is the output provided via the console; when debug mode is activated no error logs are provided in both the WooCommerce status log or on the checkout page. The loading spinner spins indefinitely and the error is never resolved.

    Uncaught (in promise) InvalidArgumentsError: One or more of the arguments needed are missing or invalid.
    at square.js?ver=4.4.1:1:355021
    at Generator.next ()
    at Rp (square.js?ver=4.4.1:1:353104)
    at s (square.js?ver=4.4.1:1:353308)
    at square.js?ver=4.4.1:1:353369
    at new Promise ()
    at square.js?ver=4.4.1:1:353248
    at Lp.verifyBuyer (square.js?ver=4.4.1:1:355381)
    at wc-square.min.js?ver=4.4.1:1:7742

Viewing 3 replies - 1 through 3 (of 3 total)
  • Zee

    (@doublezed2)

    2 years, 2 months ago

    Hello lbourgeois90,

    Thank you for contacting WooCommerce support.

    I understand you’re experiencing an issue with the WooCommerce Square plugin and I’m here to help you resolve this.

    I would like to inform you that there has been a recent update to the WooCommerce Square plugin, and the latest version is now 4.4.1. This update may include fixes that could address the issue you’re facing.

    To assist you further, I would need to take a closer look at your site’s environment. Could you please send me a copy of your site’s System Status Report? This report will give us detailed information about your setup that could be crucial for troubleshooting the problem.

    Here’s how to get the report:
    1. Navigate to your WordPress dashboard.
    2. Go to WooCommerce > Status.
    3. Click on the “Get system report” button.
    4. Then click on “Copy for support” to copy the report.

    Once you have the report, please paste it into a new Gist at https://gist.github.com. After you’ve created the Gist, you can paste the Gist link here in your reply.

    I am looking forward to your response. 🙂

    Best regards.

    Thread Starter lbourgeois90

    (@lbourgeois90)

    2 years, 2 months ago

    Thank you for your reply. Here is the report in Gist as requested: https://gist.github.com/lbourgeois90/80221365933e96a2b6cd8be9a247f6b4.

    I did update WooCommerce Square to the newest version and the console error still persists. I also uninstalled all plugins, used the basic Storefront theme and reactivated each one by one and it seems that activating TerraWallet with the new version of WooCommerce may be causing the error. My custom theme works perfectly fine with the newest version (4.4.1) of WooCommerce Square. In my current production environment I am running the newest version of TeraWallet (1.4.10) with WooCommerce Square at 4.0.0 without any errors but any upgrade beyond 4.0.0 will throw that specific error above in the console.

    anastas10s

    (@anastas10s)

    2 years, 2 months ago

    Hi there @lbourgeois90 👋

    Thank you for reaching back, with further details on this.

    I also uninstalled all plugins, used the basic Storefront theme and reactivated each one by one and it seems that activating TerraWallet with the new version of WooCommerce may be causing the error.

    From the provided information, it sounds like the culprit here is with the TerraWallet plugin. I assume WooCommerce Square was activated 2nd only to activating the WooCommerce plugin, without any issue.

    Feel free to reach out to the support channel of TerraWallet, as they would be in a better position to assist you.

    I hope this is helpful! Please let us know if you have any further questions or concerns.
    We will be happy to help you further.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Version Update causes JavaScript verifyBuyer Error’ is closed to new replies.