-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ViewException: Filament\FilamentManager::getUserName() #87
Comments
having same issue, when impersonating another guard on another panel, and then return to first panel. |
The problem is the service provider is registering the view automatically and when you use multiple guards it chokes at
the solution is overriding the service provider
and override the loading of the original service provider in composer
then you can add the view to your panel
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing this error on a testing server:
Filament\FilamentManager::getUserName(): Argument #1 ($user) must be of type Illuminate\Database\Eloquent\Model|Illuminate\Contracts\Auth\Authenticatable, null given, called in /home/forge/mysite.ie/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 355 (View: /home/forge/mysite.ie/vendor/stechstudio/filament-impersonate/resources/views/components/banner.blade.php) (View: /home/forge/mysite.ie/vendor/stechstudio/filament-impersonate/resources/views/components/banner.blade.php) (View: /home/forge/mysite.ie/vendor/stechstudio/filament-impersonate/resources/views/components/banner.blade.php) (View: /home/forge/mysite.ie/vendor/stechstudio/filament-impersonate/resources/views/components/banner.blade.php) (View: /home/forge/mysite.ie/vendor/stechstudio/filament-impersonate/resources/views/components/banner.blade.php)
I was impersonating a user when I re-migrated the database.
I think it's to do with session cookies. If I open an incognito browser then everything is fine.
Not sure what the solution is...
The text was updated successfully, but these errors were encountered: