Uncaught Snapshot missing on Livewire component with id: QAcNIGM0wsdXZxTaZYW7
Hello,
I have a widget on the dashboard panel and I run into this error:
I have logged a few lines in livewire.js
This gives me the following output:
I am not sure how to solve this.
I would like to welcome some suggestions. Thanks
52 Replies
As far as I understand Livewire a little bit each livewire component needs to have a snapshot and now this piece of code seems to be missing the snapshot. Is this correct and how can I solve this? I am using just a simple widget:
Just to be clear... if you hardcode the values in the Stat::make and uncomment the filter stuff it works normally?
Excelent question. I added some static data like the documentation:
But then I have the same error
hmmm
And without the widget everything runs smoothly?
Yes then I don't have this error
are you using the latest filament version?
Yes
do you have more widgets in your dashboard?
No just this one. And the only thing i did is add this class to
App/Filament/Widgets
And then it picked up the widget automaticallyyes because of the discoverWidgets in the PanelProvider
Right
this is weird... I think if you made a new fresh project it wouldn't be a problem
something else is causing this
Could be because I have it in more places. This is a project which I transferred over from Nova
where are you reusing it in your project?
reusing what?
ow sorry you said you had it in more places
Yeah in resources
I have tried Removing filament and installing it again but that didn't work.
and if you create a brand new widget
with only this in it
then you can figure out if it's that specific widget
Then I get the same error
What is BaseWidget?
Hmm. Should be ok then.
Yes so I have no clue on what's going on...
this is working fine for me:
what version of livewire and filament are installed
I use filament: 3.2.83
Livewire 3.5.0
it's got to be that other widget then.
the filters
Was hoping you were right:
honestly, not sure then, sorry. it's something specific to your app though. i'm not seeing that error.
does it only show when you are using the widget.
No I have seen it on more pages that's why I find it soo weird. It must be something wrong with the installation but not sure what...
* I have republished the assets
* Removed the vendor directory and did a
composer install
what is there to do elseit could be coming from a plugin too.
no plugins installed
something is adding a livewire component that probably needs a wire:key. just have no clue what it could be.
inspect the html and find that livewire id on the page, that might help to track it down
Did you try it disabling database notifications in your panel?
I removed
->databaseNotifications();
from the config file but the message is still theredid you try the stats in a fresh filament install?
No not yet. But the're are more problems on other resources. For Example I have resources with Relationmanagers there I get the same type of error. Maybe I sould create a fresh filament installation and port everything over. Unless there is an easier way to sort of reset everything
try to create a fresh install..
@Leandro Ferreira @awcodes just had time to check it on a fresh install and in a fresh install it all works smoth
This is why Filament requires a minimal repository to reproduce the issue before opening an issue on GitHub.
Are you loading app.js into your filament panel?
Nope
some extra configs, providers, plugins ?
I have removed the filament configs. And As far as I can see no extra configs...
It is sooo sooo weird
are you manually initializing Alpine anywhere?
or using a custom layout?
@awcodes not initializing Alpine. And no Custom Layout.
We're having the same issue right now and seems like we have a similar setup. Brand new widget on our dashboard page. Livewire doesn't seem to want to work at all. Any updates or fixes on your end @JJSanders?
Livewire 3.5.6
Filament 3.2.111
Attn: @Gavrisimo
what is your APP URL ?
We're using laravel herd so it's set to https://admin.test
i guess at this point its best to make a repository to reproduce the same error so we can debug it
@Gavrisimo was able to find the issue. It was the laravel-blade-comments package:
https://github.com/spatie/laravel-blade-comments/issues/6
Posting in case it helps anyone else 👍
Thank you. It's help me .