Action button Action::NEW disappeared on all crud index pages

[pfpro]

After updating to easyadmin 4.26.0 the "NEW" action buttons on all my crud index pages have disappeared, and the global-actions container is empty:

<div class="global-actions"></div>

Anyone else?

[javiereguiluz]

Strange. I can't reproduce this on my apps using EasyAdmin 😐

Let's see if others can help us debug this. Thanks!

[pfpro]

4.26.1 solved the problem, thx javier!

[pfpro]

I guess I wasn't paying enough attention. I downgraded to 4.26.0 again for testing purposes, and there were no problems. Maybe it was the cache.

[ThomasBerends]

Not sure what's happening here. Got the same problem. Upgrading to v4.26.5 gives no New action. Downgrading to v4.25.1 makes them return.

It's a basic admin with just a few fields. The only special thing is we have two admins (and thus admincontrollers, crudcontrollers, etc.) in this project.

Cache:clear does not fix it.

@javiereguiluz Tagging since I cannot reopen the issue.

[pfpro]

And when you delete and restore builds or bundles folder?

[ThomasBerends]

@pfpro Can confirm this solves it. For whoever finds this:

Steps to fix:

• Remove the bundles folder inside of /public.
• Run php bin/console assets:install
• Run php bin/console cache:clear

--

I'm not sure however why that didn't happen when the package changed though, but that seems more of a Symfony question.

[InformatiqueProg]

Same problem, upgrade to 4.25.6

Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 1 update, 0 removals
  - Upgrading easycorp/easyadmin-bundle (v4.24.6 => v4.26.5)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 1 update, 0 removals
  - Downloading easycorp/easyadmin-bundle (v4.26.5)
  - Upgrading easycorp/easyadmin-bundle (v4.24.6 => v4.26.5): Extracting archive
Generating autoload files
92 packages you are using are looking for funding.
Use the `composer fund` command to find out more!

What about running composer global require symfony/thanks && composer thanks now?
This will spread some 💖  by sending a ★  to the GitHub repositories of your fellow package maintainers.

Run composer recipes at any time to see the status of your Symfony recipes.

Executing script cache:clear [OK]
Executing script assets:install public [OK]

No security vulnerability advisories found.

no "new button" ...

i have just do a cache clear

 // Clearing the cache for the dev environment with debug true

 [OK] Cache for the "dev" environment (debug=true) was successfully cleared.

reload page... and buttons are back