What triggers `Serialization of 'Closure' is not allowed` when using Queue?

Can you please show your job class?

Hi good morning @nakov

Well, interestingly I noticed the listener did not have a queue setup on it by default - I added that. Could not find a job in the vendor directory as it does not appear to ship with a laravel implementation.

Is the registered email something that should not be queued? The out of the box registered event has a use Illuminate\Queue\SerializesModels; statement.

I'm in the weeds here with familiarity.

<?php

namespace Illuminate\Auth\Listeners;

use Illuminate\Auth\Events\Registered;
use Illuminate\Contracts\Auth\MustVerifyEmail;
use Illuminate\Contracts\Queue\ShouldQueue;

class SendEmailVerificationNotification implements ShouldQueue
{
    /**
     * Handle the event.
     *
     * @param  \Illuminate\Auth\Events\Registered  $event
     * @return void
     */
    public function handle(Registered $event)
    {
        if ($event->user instanceof MustVerifyEmail && ! $event->user->hasVerifiedEmail()) {
            $event->user->sendEmailVerificationNotification();
        }
    }
}

@nakov So what you asked hit me this afternoon.

I need to implement a job.

I've started a class InvitedUserRegisteredEmail implements ShouldQueue job but I'm wondering how would that work?

The Registered event fires: SendEmailVerificationNotification::class,. Not sure where or if something like SendEmailVerificationNotification::dispatch(); is a reasonable thing to do as the listener is already picking up on the event.

Have you created anything like this before that might cause the error Serialization of 'Closure' is not allowed?

@trevorpan if the code that you've shared above is the one that is hitting the error I really don't know how. Because you don't send any job from there. I thought you had your own job created before that was causing the error. So now you either have something Custom in the User model that throws the error, or check what you use for a Queue driver then, make sure you have it setup as it should be.

I didn't had any problem with sending email verifications before.

ok @nakov , thank you for sharing some ideas.

well this is what I've got for phpunit.xml <env name="QUEUE_CONNECTION" value="sync"/>

and in the config/queue.php

 'default' => env('QUEUE_CONNECTION', 'redis'),
...
 'connections' => [
        'redis' => [
            'driver' => 'redis',
            'connection' => 'default',
            'queue' => 'default',
            'retry_after' => 90,
            'block_for' => 5,
        ],

Pretty standard ... not sure.

// user.php
class User extends AuthUser implements Authenticatable, MustVerifyEmail
{
    use  Notifiable, HasRoles;
...

The only other thing that I'm thinking could be the routes.web: Route::middleware(['verified'])->group(function () {...

Could the route group cause this?

possibly this explains it?

https://laracasts.com/discuss/channels/laravel/troubleshooting-serialization-of-closure-is-not-allowed-issue-when-caching-routes

Would re-using the register method on the RegistersUsers trait cause this?

Route::post('/invitations/register', 'Auth\InvitationsRegisterController@register');

@nakov really appreciate your taking a stab at this. It helped me think about other possibilities. In the end, at least it appears, the InvitationsController was using the out of the box Laravel register method. I mistakenly believed I could reuse it.

From what I can see the route cannot be used twice.

The error message is not sufficiently descriptive - possibly worth doing a PR on github and try to improve the message.

So, in the InvitationsController I omitted the protected function validator(array $data) and condensed it to:

/**
     * Create a new user instance after a valid registration.
     *
     * @param Request $data //changed from array $data
     * @return User
     */
    protected function create(Request $data) //changed from array $data
    {
        $invitation = Invitation::findByInvitationCode(request('invitation_code'));
        abort_if($invitation->hasBeenUsed(), 404);

        request()->validate([
            'firstname' => 'required|string|max:255',
            'lastname' => 'required|string|max:255',
            'email' => 'required|string|email|max:255|unique:users',
            'password' => 'required|string|min:12|confirmed',
        ]);

        $user = User::create([
            'firstname' => $data['firstname'],
            'lastname' => $data['lastname'],
            'email' => $data['email'],
            'password' => Hash::make($data['password']),
        ]);

        event(new Registered($user)); // a key addition

        $invitation->update([
            'user_id' => $user->id,
        ]);

        return view('auth.verify');
    }