Laravel 5.7 - Access Auth::User() inside a service provider

Question

I need to access to the current user in a service provider of a module. The Auth::user() returns null. I know the middleware is called after the service provider and that is why this is null. Is there any solution to this problem? it is my code

namespace Modules\User\Providers;

use Illuminate\Support\Facades\Auth;
use Illuminate\Support\ServiceProvider;
use Nwidart\Modules\Facades\Module;

class ViewComposerProvider extends ServiceProvider
{
    /**
     * Indicates if loading of the provider is deferred.
     *
     * @var bool
     */

    protected $defer = false;

    /**
     * Register the service provider.
     *
     * @return void
     */

    public function boot()
    {
        $this->buildMenu();
        $this->buildAvatar();
    }

    public function register()
    {
        dd(Auth::user());//null
    }

    private function buildAvatar(){
        $f = Auth::user();
        dd($f); // null
    }

    public function buildMenu()
    {
        view()->composer('layouts.subnavbar', function ($view) {
            $t = \Nwidart\Modules\Facades\Module::getByStatus(1);
            $modules = [];
            foreach ($t as $item)
                $modules[] = $item->name;
            $view->with('modules', $modules);
        });
    }

    /**
     * Get the services provided by the provider.
     *
     * @return array
     */
    public function provides()
    {
        return [];
    }
}

Possible duplicate of Laravel 5.3: How to use Auth in Service Provider? — Cory Fail
– Cory Fail, Commented Nov 6, 2018 at 15:47
You should be doing this in the middleware, not the service itself. — Cory Fail
– Cory Fail, Commented Nov 6, 2018 at 15:49
Possible duplicate of using auth in laravel service provider — Kyle Wardle
– Kyle Wardle, Commented Nov 6, 2018 at 15:55

MrChrissss · Accepted Answer · 2018-11-06 16:00:56Z

2

Instead of calling the user in the provider you could make 2 view composers, 1 for the menu and 1 for the avatar

AvatarComposer.php

class AvatarComposer
{

    public function compose(View $view)
    {
        $avatar = Auth::user()->avatar//AVATAR HERE
        $view->with('avatar', $avatar);
    }
}

ModuleComposer.php

class ModuleComposer
{
    public function compose(View $view)
    {
        $t = \Nwidart\Modules\Facades\Module::getByStatus(1);
        $modules = [];
        foreach ($t as $item)
            $modules[] = $item->name;
        $view->with('modules', $modules);
    }
}

and then in the boot of your provider:

//make it public for all routes
View::composer('*', AvatarComposer::class);

View::composer('layouts.subnavbar', ModuleComposer::class);

answered Nov 6, 2018 at 16:00

MrChrissss

2911 gold badge2 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

M a m a D Over a year ago

The classes should extend serviceprovider?

MrChrissss Over a year ago

No, you can check the documentation here: laravel.com/docs/5.7/views#view-composers

M a m a D Over a year ago

well, it is class ComposerServiceProvider extends ServiceProvider

MrChrissss Over a year ago

The ServiceProvider where you write View::composer must inject the serviceprovider indeed

MrChrissss Over a year ago

The composer will be called after everything is imported including the auth, you can find the explanation here: laravel.com/docs/5.7/providers#the-boot-method

|

Collectives™ on Stack Overflow

Laravel 5.7 - Access Auth::User() inside a service provider

1 Answer 1

7 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

7 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related