Auth::user()->id 返回“试图获取非对象的属性”——Laravel 5.8

Question

UPDATED 2

I made like and unlike method. But when I try to like the article, it returns an error. Route [login] not defined.

I am using passport API login. I am giving token for login etc... I login without a problem. I see the the pages only auth user can see. But it seems when I like the article, Auth:: doesn't understand user logged in or not. Maybe this is the problem. Because I am using Passport? So in the controller instead of Auth::

I used it like $user = $request->user(); (you can see the controller below.) But still same error popping when I like the article. Route [login] not defined.

controller

public function postLikeArticle( Request $request, $articleID )
{
    $article = Article::where('id', '=', $articleID)->first();
    $user = $request->user();

    $article->likes()->attach( $user->id, [
        'created_at'    => date('Y-m-d H:i:s'),
        'updated_at'    => date('Y-m-d H:i:s')
    ]);

  return response()->json( ['article_liked' => true], 201 );
}

public function deleteLikeArticle( Request $request, $articleID )
{
    $article = Article::where('id', '=', $articleID)->first();
    $user = $request->user();

    $article->likes()->detach( $user->id );

    return response(null, 204);
}

Routes

Route::middleware('auth:api')->group(function() {
    Route::get('/user', function (Request $request) {
        return $request->user();
    });

    Route::get('/articles/{id}/like', 'Api\ArticlesController@postLikeArticle');
    Route::get('/articles/{id}/like', 'Api\ArticlesController@deleteLikeArticle');

});

If you need to see anymore file. please name it in the comment.

Answer 1

Your routes for like/dislike are not auth protected which means that the user might not be logged in, so you can group all routes requiring an authenticated user like this:

// public routes out of the group, for example:

Auth::routes();

Route::middleware('auth:api')->group(function() {
    Route::get('/user', function (Request $request) {
        return $request->user();
    });

    Route::get('/articles/{id}/like', 'Api\ArticlesController@postLikeArticle');


    // you cannot have same routes for both, so this
    // Route::get('/articles/{id}/like', 'Api\ArticlesController@deleteLikeArticle');
    // should be this:
    Route::get('/articles/{id}/dislike', 'Api\ArticlesController@deleteLikeArticle');

});

Then either: Auth::id() or Auth::user()->id should give you the same. Or even the helper function so you don't need to worry for the imports..

auth()->id();

// or
auth()->user()->id;

Answer 2

If you need the user to be authenticated then you need to be using the middleware that ensures that. In addition you need to also ensure that you are using the correct HTTP verbs depending on what you need to do, if anything your current definition is creating a conflict:

Route::middleware('auth:api')->post('/articles/{id}/like', 'Api\ArticlesController@postLikeArticle');
Route::middleware('auth:api')->delete('/articles/{id}/like', 'Api\ArticlesController@deleteLikeArticle');

You also need to ensure your front-end is using the correct verbs as well.

There are two reasons:

1. If you don't use the middleware you're basically saying those routes don't require authentication
2. If you're using the API guard to authenticate users then you need to explicitly use the auth:api middelware otherswise Laravel will attempt to authenticate the user using the default guard which is usually the session. When using an API you should not use the session

Answer 3

instead of

Auth::user()->id

You can try this

auth()->user()->id

you can refer laravel documentation for more information

Answer 4

Few simple points should resolve your confusion:

1. "Trying to get property of a non object" means, Auth::user() is not an object which means it's null, you are trying to access a route publicly which needs an authenticated user which leads to our next point.
2. Routes which use functions postLikeArticle() and deleteLikeArticle() should be inside the authorization middleware 'auth:api'
3. You are using method get for both of your routes which use above functions, one should be using delete method.
4. You can use Auth::id() as a substitute of Auth::user()->id just to be short hand.

When using PASSPORT for authentication, you do not follow the usual Laravel way of user authorization hence Auth::user() is useless. In order to fetch the authenticated user, you need to use:

$user = $request->user();

Where $request is an instance of Illuminate\\Http\\Request

Here is an example for you: Import the Request class in the beginning of the controller file:

use Illuminate\\Http\\Request;

and your controller logic:

public function postLikeArticle( Request $request, $articleID )
{
    $article = Article::where('id', '=', $articleID)->first();
    $user = $request->user();

    $article->likes()->attach( $user->id, [
        'created_at'    => date('Y-m-d H:i:s'),
        'updated_at'    => date('Y-m-d H:i:s')
    ]);

  return response()->json( ['article_liked' => true], 201 );
}

public function deleteLikeArticle( Request $request, $articleID )
{
    $article = Article::where('id', '=', $articleID)->first();
    $user = $request->user();

    $article->likes()->detach( $user->id );

    return response(null, 204);
} 

I hope it helps