[v3] i get this error in the console "Could not find Livewire component in DOM tree" when i delete a record from the table

[tabatii]

Package

filament/tables

Package Version

v3.3.45

Laravel Version

v12.42.0

Livewire Version

v3.7.1

PHP Version

8.3.22

Problem description

when i delete a record from a filament table i get this error in the screenshot below

i noticed the error first on an old filament 3 project and i created a fresh laravel project with a fresh filament 3 installation to confirm the problem and it happend also in the fresh project

Expected behavior

i expect the record to be deleted with no console errors

Steps to reproduce

1. Clone the repo
2. Migrate the database
3. Create a filament user
4. Run the seeders
5. Login to the dashboard
6. Go to the posts resource and open the browser console
7. Delete a post from the filament table and you will see the browser console errors

Reproduction repository (issue will be closed if this is not valid)

https://github.com/tabatii/filament-bug

Relevant log output

[Cornelis19]

This bug also impacts us; executing any action in our panels results in this console error.

[kl4ver]

We also have issues with this bug

[Cornelis19]

@danharrin It looks like some modal table actions are leaving the table in a stale state (content doesn’t refresh after the action completes).

for context, im using this to render my relation manager in the form:
https://github.com/njxqlus/filament-relation-manager-component
\Njxqlus\Filament\Components\Forms\RelationManager,

In some cases the table only updates if I call resetTable() manually; so that's my fix for now

[danharrin]

Can you downgrade Livewire and see if that caused it maybe? We haven't made changes to v3 recently

[Cornelis19]

@danharrin
Version v3.3.26 works in our case; but v3.3.45 and v3.3.43 doesn't.
The issue is between those versions.

[danharrin]

These versions were released ages ago though, why are these issues only being reported in the last 3 days? Have you checked the latest Livewire releases?

[Cornelis19]

@danharrin found it:
This is a compatibility issue between Filament v3.3.x and Livewire v3.6–3.7, where modal-based actions sometimes leave tables in a stale state or throw “Could not find Livewire component in DOM tree” errors. This doesn’t only affect relation managers, but also resource delete actions, so it seems related to the core modal/action lifecycle. It would be great if this could be investigated or better supported across these Livewire versions.
for now we will use 3.6.4