Spinning block in checkout editor page (5801)

[ebinnion]

Describe the Bug

On a fresh install of WordPress, with the latest WooCommerce and PayPal Payments extensions, I notice that there's an infinitely spinning spinner in the checkout page editor. The spinning block in question is the pay later block.

To Reproduce

1. Create a new site
2. Install WooCommerce and skip guided setup
3. Install the PayPal Payments extension and connect to PayPal
4. Click the pages menu item
5. Open the checkout page
6. Verify the spinner does not go away

Screenshots

Expected Behavior

I would expect that the spinner briefly loads and then goes away.

Actual Behavior

Spinner doesn't stop loading.

Environment

• WordPress Version - 6.9
• WooCommerce Version - 10.4.3
• Plugin Version - 3.3.2
• Browser [e.g. Chrome, Safari] and Version - Chrome 144.0.7559.97
• Any other plugins installed - Jetpack/Akismet

Additional Details

System status

<!--If applicable, paste the system status here. Please ensure you redact or remove any identifying information. -->

[InpsydeNiklas]

Hey @ebinnion, thanks for reporting this!
The Pay Later messaging block has eligibility requirements that can't always be resolved in the editor context, including merchant account status, visitor geolocation (e.g., US accounts only show messaging to US visitors), and other store configurations.
I'm unable to reproduce any abnormal behavior in the latest WordPress Playground, so if you could check the browser console while the spinner is loading, eventual PayPal SDK warnings/errors may give a better insight into why the messaging did not load on your end.

In any case, since there are legitimate scenarios where messaging won't render, we intentionally keep the block in place so merchants retain control. But you're right, an infinite spinner is poor UX.
We created a ticket to improve this: timeout after a few seconds → show a static placeholder explaining that messaging preview isn't available in the editor at this time. Merchants can still configure the block, and it'll render correctly on the frontend when conditions are met.

[ebinnion]

I do see this JS error on this page:

I'm not really seeing anything else that stands out as an error in the console.

[ebinnion]

Hey @InpsydeNiklas - I just wanted to check on the status of the ticket internally for creating the placeholder?

[SydeKrystian]

Hi @ebinnion

Since Niklas is out of the office for the next few days, I checked Jira, and the issue is currently in the “Selected TODO” stage. This usually means it is planned and will most likely be fixed in an upcoming release.

Kind regards,
Krystian