Please Enter Address To Continue

I’m running into the same issue… the refresh allows it to work for some reason, but it’s not a good solution as it makes the store feel less credible. Great plugin, just hoping this new error can be handled. Thank you!

Thank you for letting me know. I spent hours yesterday trying to figure out the problem. I had to temporary switched to “Payment Plugins for PayPal Woo Commerce” until this problem gets fixed. Yes, I agree. It is a great plugin but this can be frustrating and cause us to lose sales. I hope they fix it soon too. If your site works again, please let us know.

• This reply was modified 2 years, 3 months ago by Jazz.

I am getting the same error when I do a test order. I just installed this plugin today, and I am switching back to PayPal Standard for the foreseeable future.

Getting the same errors myself and shocking that the plugin creator isn’t answering.

Hi @prgemini,

We regret to hear if you’re encountering any issues after the most recent update and suggest giving it a try with the previous version 1.9.5. Older plugin versions can always be downloaded from the bottom of this page.

It’s not clear if the cause for the behavior is the same for everyone in this thread, but @sreford seemingly could work around the issue by selecting Force shipping to the customer billing address in the WooCommerce shipping options.

In any case, it doesn’t seem like I can reproduce the behavior in my own environment yet, which usually points towards this being either caused by a specific configuration or a potential conflict with a different plugin or the theme.
If you could please share with us a copy of your WooCommerce system report, we can get a better idea about similarities between the affected sites.
You can share the system report either here in the forums or privately with us from here: https://paypal.inpsyde.com/docs/request-support/
If you send a private message, please include a link to this thread.
Thanks!

Kind regards,
Niklas

@niklasinpsyde Hello! Thank you for your reply. The error might not be showing on your end because I deactivated the plugin. I am using a different plugin in the meantime. Do I need to reinstall the plugin for the system report?

Sorry but I do no like to force billing address because I have customers who purchase my items as gifts and ship to different address.

I might just revert back to the older version, which I didn’t have any problems with before. Is the older version safe to use? Free of bugs, etc? Thanks again

Hi @prgemini,

The error might not be showing on your end because I deactivated the plugin. I am using a different plugin in the meantime. Do I need to reinstall the plugin for the system report?

I don’t know the URL to your website, but this is included in the WooCommerce system report.
The system report can be accessed from here:
WooCommerce > Status > Get system report > Copy for support
You can share it here in the forums or privately from here: https://paypal.inpsyde.com/docs/request-support/
The PayPal Payments gateway does not need to be enabled, but when the plugin is active, it will add additional useful information to the report.

Using a different PayPal integration is a legitimate workaround in case you’re having any issues with PayPal Payments. But we’d be happy to learn more context about the issue you’re facing, so we can provide a proper solution for you and potentially other affected users.

Sorry but I do no like to force billing address because I have customers who purchase my items as gifts and ship to different address.

This is not meant as a permanent solution, but only as a way to test if this problem still persists when using this configuration. The plugin should be working in every WooCommerce configuration, but it’s impossible for us to test all possible combinations with third-party plugins, so we have to better understand the similarities between the issue reports.

I might just revert back to the older version, which I didn’t have any problems with before. Is the older version safe to use? Free of bugs, etc?

You can safely roll back to the previous version 1.9.5, but I recommend saving the plugin settings in the “Standard Payments” tab after downgrading.
No software is entirely free of bugs, and it’s always a question of context. If you didn’t have any problems previously, then there is little reason to suddenly encounter problems with the same version.
Most fixes or enhancements mentioned in the changelogs usually mean one issue less compared to the previous version. But whether a specific fix impacts your particular site, is something we can’t fully judge.

For example, the Checkout field validation behavior was modified in the latest update, which improved the compatibility with certain third-party plugins.
This was tested thoroughly, but a change that improves compatibility with one other configuration or plugin may cause compatibility problems with another one. Since PayPal Payments is by the most prevalent PayPal integration, there may always be an ever-rotating subset of users that encounter a specific problem on their site configuration with a particular plugin version.
But the team is here to help you out with if you have any questions.

Kind regards,
Niklas

I am experiencing the same issue. Haven’t gotten anywhere with PayPal or WooCommerce support.

I temporarily solved the issue by changing the WooCommerce setting for Default customer location to Shop country/region. I know this isn’t possible for all stores, but it did solve this issue for me, oddly enough.

Hi everyone,

This issue can be worked around as mentioned above or with a downgrade to the previous version 1.9.5. The upcoming update 2.0.1 includes a fix and is expected to be released in the coming days, so we’ll mark this resolved already.
There is a pre-release version available for testing here on GitHub, in case anyone wants to give this a try.
Feedback about how this works for you is appreciated in any case.
Thanks!

Kind regards,
Niklas