FATAL ERROR + BUG. Shipstation conflict action

Any update on this please, we have also encountered this issue, its causing on our instance the tracking orders duplicating multiple times.

Hello @bonsaigroup & @alexs4

Thanks for reaching out to us, we’re here to help.

I can confirm that the issue you encountered with version 2.7.1 has been identified and resolved in the upcoming release candidate of version 2.8.0. To proceed, I recommend testing the release candidate version 2.8.0 which is available for download here: Download 2.8.0-rc1.

Please install this version and let us know how it performs in your environment. If you encounter any further issues or need additional assistance, please do not hesitate to contact us.

Kind Regards,
Krystian

@inpsydekrystian Thank you for your quick response and solution. We’re glad we were able to point this out to you so that others don’t suffer.

I am having the same issue with the WooCommerce Shipment Tracking Plugin. It sounds like the same bug, with the same message appearing in the logs. Should I expect the update to also correct the conflict with this plugin?

Thanks!

edit: After doing some digging on the GitHub page, it looks like it is the same issue. I downgraded rather than upgraded to resolve the issue.

• This reply was modified 5 months, 2 weeks ago by Sam Wave.

@nextwavingit Best to update the app and see.

This error is a live error on every production site that has paypal:

2024-06-06T00:08:12+00:00 Critical Uncaught InvalidArgumentException: PayPal order ID not found in meta.

… is looking for order meta ID on orders that are not yours (facepalm) and then breaking without error catching (facepalm), causing tons of stuff downstream (shipstation etc) to break (triple facepalm!).

For us, this caused us to send 17,000+ fng emails to customers OVER AND OVER again because shipstation couldn’t get a proper confirmation of notification – and that’s just on ONE website that only makes a few orders a day. 17 thousand freakin emails! Practically got us blacklisted from our email provider.

You programmed this as if only PayPal can be the order processor and nothing else without thinking about whether or not this could break stuff, which is like, the main job of a good programmer.

PLEASE don’t hook every order – ever – stick to your own orders, please!

UPDATE 6/11/24: Paypal release 2.8.0 with the fix for this issue.

• This reply was modified 5 months, 2 weeks ago by mystyleplatform. Reason: update

Hello,

I’m marking this thread as resolved since the issue has been addressed in the latest release. If the problem persists, users likely need to update the plugin.

Kind regards,
Krystian