【Laravel5.7.28】Auth機能の会員登録時にSessionGuardのエラーが発生してしまう

Question

Laravelの認証機能(Auth)をphp artisan make:authで導入致しまして、
実装を進めておりましたが、会員登録後に
以下のエラーメッセージが発生してしまっております。

usersテーブルに新規データは登録できており、登録後の認証周りでエラーが発生しており、
恐らく/config/auth.phpの設定か/app/User.phpの記載内容に誤りか不足があるかなと思うのですが、具体的な修正箇所の特定ができておらず、お知恵をお借り出来ますと幸いです。。

認証関連の基礎的な部分を勉強し直しておりますが、もしよろしければご指摘を
頂けますと有り難いです。
どうぞ宜しくお願い致します。

＜エラーメッセージ＞

Symfony \ Component \ Debug \ Exception \ FatalThrowableError (E_RECOVERABLE_ERROR)
Argument 1 passed to Illuminate\Auth\SessionGuard::login() must be an instance of Illuminate\Contracts\Auth\Authenticatable, instance of App\Model\User given, called in /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Auth/RegistersUsers.php on line 34

＜/var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Auth/RegistersUsers.php on line 34＞
以下の$this->guard()->login($user);でエラーが発生しております。

    public function register(Request $request)
    {
        $this->validator($request->all())->validate();
        event(new Registered($user = $this->create($request->all())));

        $this->guard()->login($user);

        return $this->registered($request, $user)
                        ?: redirect($this->redirectPath());
    }

＜/var/www/html/vendor/laravel/framework/src/Illuminate/Auth/SessionGuard.php
＞
呼び出し先の箇所は以下になります。

    public function login(AuthenticatableContract $user, $remember = false)
    {
        $this->updateSession($user->getAuthIdentifier());

        // If the user should be permanently "remembered" by the application we will
        // queue a permanent cookie that contains the encrypted copy of the user
        // identifier. We will then decrypt this later to retrieve the users.
        if ($remember) {
            $this->ensureRememberTokenIsSet($user);

            $this->queueRecallerCookie($user);
        }

        // If we have an event dispatcher instance set we will fire an event so that
        // any listeners will hook into the authentication events and run actions
        // based on the login and logout events fired from the guard instances.
        $this->fireLoginEvent($user, $remember);

        $this->setUser($user);
    }

＜/app/User.php＞

<?php namespace App;

use Illuminate\Auth\Authenticatable;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Auth\Passwords\CanResetPassword;
use Illuminate\Contracts\Auth\Authenticatable as AuthenticatableContract;
use Illuminate\Contracts\Auth\CanResetPassword as CanResetPasswordContract;
use Laravel\Cashier\Billable; //Stripe用

use Illuminate\Notifications\Notifiable;

class User extends Model implements AuthenticatableContract, CanResetPasswordContract {
	use Billable; //Stripe用
	use Authenticatable, CanResetPassword;

	use Notifiable;

	/**
	 * The database table used by the model.
	 *
	 * @var string
	 */
	//protected $table = 'users';

	/**
	 * The attributes that are mass assignable.
	 *
	 * @var array
	 */
	protected $fillable = ['name', 'email', 'password', 'login_type', 'social_id', 'created_at', 'email_social', 'image'];

	/**
	 * The attributes excluded from the model's JSON form.
	 *
	 * @var array
	 */
	protected $hidden = ['password', 'remember_token'];

}

＜/config/auth.php＞

<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Authentication Defaults
    |--------------------------------------------------------------------------
    |
    | This option controls the default authentication "guard" and password
    | reset options for your application. You may change these defaults
    | as required, but they're a perfect start for most applications.
    |
    */

    'defaults' => [
        'guard' => 'web',
        'passwords' => 'users',
    ],

    /*
    |--------------------------------------------------------------------------
    | Authentication Guards
    |--------------------------------------------------------------------------
    |
    | Next, you may define every authentication guard for your application.
    | Of course, a great default configuration has been defined for you
    | here which uses session storage and the Eloquent user provider.
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | Supported: "session", "token"
    |
    */

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
        'api' => [
            'driver' => 'token',
            'provider' => 'users',
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | User Providers
    |--------------------------------------------------------------------------
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | If you have multiple user tables or models you may configure multiple
    | sources which represent each model / table. These sources may then
    | be assigned to any extra authentication guards you have defined.
    |
    | Supported: "database", "eloquent"
    |
    */

    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\User::class,
        ],

//         'users' => [
//             'driver' => 'database',
//             'table' => 'users',
//         ],
    ],

    /*
    |--------------------------------------------------------------------------
    | Resetting Passwords
    |--------------------------------------------------------------------------
    |
    | You may specify multiple password reset configurations if you have more
    | than one user table or model in the application and you want to have
    | separate password reset settings based on the specific user types.
    |
    | The expire time is the number of minutes that the reset token should be
    | considered valid. This security feature keeps tokens short-lived so
    | they have less time to be guessed. You may change this as needed.
    |
    */

    'passwords' => [
        'users' => [
            'provider' => 'users',
            'table' => 'password_resets',
            'expire' => 60,
        ],
    ],

];

Answer 1

Userモデルが旧バージョン時の書き方のままなのでまず最新バージョンに合わせる。
https://github.com/laravel/laravel/blob/master/app/User.php

エラーメッセージのApp\Model\Userだけ他と違うのでどっちが正しいのか分からない…。
元のUserをapp/Model/User.phpに移動したのなら
User.phpのnamespaceと
auth.phpの'model' => App\User::class,の変更が必要。
stripe使ってるならservices.phpのUserも。

Comments

[退会済みユーザー]

早々にありがとうございます！ご教示頂いた内容にて
修正をしてみます！

[退会済みユーザー]

上記の修正を実施したところエラーが解消致しました。
ご指摘頂きありがとうございました！