You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having the same issue after a fresh installation and simply adding the Tapp\FilamentAuditing\RelationManagers\AuditsRelationManager relation manager to a model resource in Filament.
Navigating to the relation manager tab on the model resource causes the exception
Unable to find component: [tapp.filament-auditing.relation-managers.audits-relation-manager]
Seems related to Flare according to the stack trace... I'm not even using Flare. (Flare is appearing in the stack trace, but not the source of the component not found error..)
The exception occurs from Livewire\Mechanisms\ComponentRegistry->getNameAndClass method. Below is a snapshot of a debugging session.
// Notice how the argument to the function is as follows:$nameComponentOrClass = "tapp.filament-auditing.relation-managers.audits-relation-manager";
// Which causes the first `is_subclass_of()` check to fail, which converts to a "class" name$class = "\App\Livewire\Tapp\FilamentAuditing\RelationManagers\AuditsRelationManager";
// but this is not the correct namespace for the relation manager, so the check for class_exists() fails, which appends \\Index//Finally the 2nd check for `is_sublass_of()` fails, causing ComponentNotFoundException to be thrown.
On clicking Restore button, Unable to find component: [tapp.filament-auditing.relation-managers.audits-relation-manager] error occurs.
The text was updated successfully, but these errors were encountered: