Block inserter not being displayed when WP filter allowed_block_types_all is used (Core 6.6.2)

[sweco-seerjf]

Description

Hi,

We are using ACF to create the blocks on our websites. To remove the default blocks we are also using the filter allowed_block_types_all.
But after upgrading WP Core to 6.6.2 the block inserter below the blocks is no longer displayed after inserting the first block. (Please see the screenshot section)

When I remove the allowed_block hook the inserter is displayed again but a different (default?) version:

The array coming out from allowed_block_types_all filter after removing default blocks looks something like this:

Digging through the code in block-editor.js I was able to find the condition in the function Items() that might be problematic:

Just returning true here makes the block inserter to display properly again:

Returning true on either side of the && in the highligted condition does not seem to work. Both sides need to return true.

Note:
I have tried downgrading ACF but still same issue. Using WP Core 6.5.5 is working as usual.

I hope that this is enough information to backtrack from here. Thanks in advance!

Step-by-step reproduction instructions

1. Create a custom ACF block
2. Use the filter "allowed_block_types_all" to only return the newly created block
3. Go to create new page
4. Add the first block
5. Now the inserter should have been removed.

Screenshots, screen recording, code snippet

Environment info

Environments:
Wordpress 6.6.2

Plugins:
Advanced Custom Fields PRO 6.3.9

Theme
Custom theme

Browsers:
Edge - Version 130.0.2849.56
Chrome - Version 130.0.6723.71
Firefox - Version 122

Please confirm that you have searched existing issues in the repo.

• Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

• Yes

Please confirm which theme type you used for testing.

• Block
• Classic
• Hybrid (e.g. classic with theme.json)
• Not sure

[virgiliud]

I am seeing a similar issue with normal non-ACF blocks

[MGabrane]

I’m experiencing the same issue

[github-actions]

Hi,
This issue has gone 30 days without any activity. This means it is time for a check-in to make sure it is still relevant. If you are still experiencing this issue with the latest versions, you can help the project by responding to confirm the problem and by providing any updated reproduction steps.
Thanks for helping out.