@jlgonzalezcaballero
same issue, experienced the issue when upgrading composer. Ran the suggested filament:upgrade, and still experienced the same issue. Ended up locking filament/tables to version
from:
"filament/tables": "^3.1",
to:
"filament/tables": "3.2.124",
then ran composer update
which outputs
Loading composer repositories with package information
Updating dependencies
Lock file operations: 0 installs, 6 updates, 0 removals
- Downgrading filament/actions (v3.2.130 => v3.2.124)
- Downgrading filament/forms (v3.2.130 => v3.2.124)
- Downgrading filament/infolists (v3.2.130 => v3.2.124)
- Downgrading filament/notifications (v3.2.130 => v3.2.124)
- Downgrading filament/support (v3.2.130 => v3.2.124)
- Downgrading filament/tables (v3.2.130 => v3.2.124)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 0 installs, 6 updates, 0 removals
- Downloading filament/support (v3.2.124)
- Downloading filament/actions (v3.2.124)
- Downloading filament/notifications (v3.2.124)
- Downloading filament/infolists (v3.2.124)
- Downloading filament/forms (v3.2.124)
- Downloading filament/tables (v3.2.124)
- Downgrading filament/support (v3.2.130 => v3.2.124): Extracting archive
- Downgrading filament/actions (v3.2.130 => v3.2.124): Extracting archive
- Downgrading filament/notifications (v3.2.130 => v3.2.124): Extracting archive
- Downgrading filament/infolists (v3.2.130 => v3.2.124): Extracting archive
- Downgrading filament/forms (v3.2.130 => v3.2.124): Extracting archive
- Downgrading filament/tables (v3.2.130 => v3.2.124): Extracting archive
then back up and running. It seems 3.2.124 > 3.2.130 has breaking changes.