Queue does not work when using custom Guards/Middleware

[johannesMEGABAD]

Hey :)

So for a project I am in need of using a custom Authguard aswell as a custom middleware to check the auth state of the user.
So far so good it works fine until I try to use the queue on the export.

It gives the message that the export has been queued but upon finishing the notification that my file is ready does not show up.
After digging I think it probably is due to the fact that the download Route uses the middlewares web and signed.

I don't have the web middleware since I am using a custom middleware. Also in the export itself it tries to get the userid by using auth()->id().
Here I aswell have a custom guard in place thus resulting in the userid being null.

Is there a fix to this? I tried to already use my custom guard in the export and also removed the middlwares in the web.php.. but still no message that my file is ready :/

[pxlrbt]

I think we need to replace any occurrences of auth()->id() with Filament::auth()->id(). Could you try whether that works?

[johannesMEGABAD]

Hey :)

When doing this it works and I get the Notification that my file is ready to download! But then.. could the occurerences of auth()->id() not be replaced by Filament::auth()->id() since it then would already know which guard to use?

[pxlrbt]

But then.. could the occurerences of auth()->id() not be replaced by Filament::auth()->id() since it then would already know which guard to use?

Yes. That's the plan. Just wanted to check whether it works before 😅

[johannesMEGABAD]

Hahaha okay well then I am glad I could help haha 😸

[pxlrbt]

I just released v2.4.3. Can you test whether that fixes your issues?

[johannesMEGABAD]

Hey :)

Yup that works perfect ^^ Thanks a lot