Anthony8Raymond

Great! THANKS!

I, too, use the LiteSpeed Cache plugin. Good observation. Thanks!

Yes, this has been happening of late. I will do my best to acquire the information for which you ask here. Thank you for your help!

My label finally became available for printing nearly twenty minutes after purchase completion. I hope you can fix this issue. Thank you!

Much like the OP’s experience, my label was ready for printing took almost twenty minutes to become available.

I am having the same issue here.

“Would you mind clearing a bit more what you’re facing and under what circumstances does this happen?”

Sure! I purchase a label. I get the email notifying me that the label purchase was approved. I am at the screen that is shown here with the “Refresh purchase status” bar doing its animation though I am not able to get to nor print the shipping label. It’s stuck.

“I’m wondering how’s that going on? Do you see any progress or it’s completely stuck?”

It is stuck in the sense that there is no label to print nor any access to it. I can back out of the page. If I refresh the page I return to the main order page. Then when I click on the “View purchased shipping label” button, I return to this page with the “Refresh purchase status” bar doing its animation.

“Also please report the WooCommerce and WooCommerce Shipping you’re using.”

I’m configured for auto-updates, so it’s the latest: WooCommerce 9.3.3 and WooCommerce Shipping 1.1.5.

Thank you for your help!

I am having the same issue. I get the same screen showing that the label is being processed. And it HANGS there. There are no error messages in the WooCommerce error log.

I found a SOLUTION!

Using the Enable jQuery Migrate Helper, I set the jQuery version to “Legacy 1.12.4-wp” and it started working.

After the update to WP 5.6, this issue has flared again. The Enable jQuery Migrate Helper plugin is not fixing the problem. Anyone got a new solution? THANKS!

Confirmed. This solution — installing the Enable jQuery Migrate Helper plugin — works, for this issue as well as the creating-a-new-category issue. Good find and fix. Thank you, mbrsolution!