-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Method [viaRemember] does not exist. #193
Comments
Maybe I got it completely wrong here, but
I can't comment on the Postman vs. test thing, but it seems your middleware and/or jwt config don't align. I'm assuming quite much here, so I apologize upfront if this the wrong direction here. |
Please share your config file. |
Not sure what happened there, because I want to use the same API route for mobile and web calls, and that works fine.
|
How does the middleware for your api and web route look like? |
This is my auth middleware |
You're using the guard for API otherwise it'll be fallback to null, can you try to define both guards on if/else? Thank you :) |
Method [viaRemember] does not exist.
I am running tests in Laravel and trying access to my API.
I am sending token with headers (code bellow), same as a normal API call from postman for example. Api call from the postman works without any errors.
Your environment:
Steps to reproduce
Try to send request from laravel test
Expected behaviour
To allow access to API same as a request from the postman or mobile app for example.
Actual behaviour
• Tests\Feature\Customer\CustomerTest > if user can get api response
Expected response status code [200] but received 500.
Failed asserting that 200 is identical to 500.
The following exception occurred during the last request:
The text was updated successfully, but these errors were encountered: