302 redirect causes an error when using web and auth middlewares

@s4muel Hi, it returns a view in the form

return view('mypackage::my.view', ['my'=>'params']);

It is plainly not working, I even tried this:

Route::middleware(['auth'])->group(function() {
    Route::get('whatever', function(){
        return '1';
    });
});

And the same result, I was initially thinking my custom package may have something to do with this so I installed laravel in a new subdomain, tested the auth routes and they worked, I then added my package and it continued to work so right now I have two installs which appear identical (obviously there is something different) one works and the other does not.

I tried clearing the cache, nothing.

My best guess is that the laravel install is corrupted or the particular version has a problem with it, the installs are about 2 weeks apart though and the about command shows the exact same version for everything so I am sticking with corrupted files, maybe a file I worked on got corrupted during upload??

I will keep this open for some time to see if anyone has had a similar issue or in case my issue returns faster than expected.

@tlacaelelrl Any chance you can share the error page so we can look through the stack trace. In laravel 9 there is a share button

@Sinnbeck this is it:

https://flareapp.io/share/17DqlOE5

The last routes file I tested with is this:

<?php

use Illuminate\Support\Facades\Route;

Route::middleware(['auth'])->group(function() {
    Route::get('whatever', function(){
        return '1';
    });
});
Route::get('login', function(){
    return '1';
})->name('login');

@tlacaelelrl the return seems fine. since it fails having the right object to add headers in VerifyCsrfToken middleware only when the auth middleware is used, i would check there. App\Http\Middleware\Authenticate class, out of the box, is:

<?php

namespace App\Http\Middleware;

use Illuminate\Auth\Middleware\Authenticate as Middleware;

class Authenticate extends Middleware
{
    /**
     * Get the path the user should be redirected to when they are not authenticated.
     *
     * @param  \Illuminate\Http\Request  $request
     * @return string|null
     */
    protected function redirectTo($request)
    {
        if (! $request->expectsJson()) {
            return route('login');
        }
    }
}

don't you override some methods in there, so it returns something suspicious? i would just debug around there and check what is returned. at first AuthenticationException should be thrown (in Illuminate\Auth\Middleware\Authenticate) and then "converted" to redirectResponse to the page defined in the redirectTo() method.

@s4muel The middleware is not modified but you made me think about the things I did modify, in this case

App\Exceptions\ExceptionHandler

I have some custom exceptions which are documented so the employees can easily fix, I have this:

<?php

namespace App\Exceptions;

use ...;

class Handler extends ExceptionHandler
{
    public function render($request, Throwable $e):Response|JsonResponse
    {
        /**
         * Custom error code handler
         */
        $exception = $this->prepareException($this->mapException($e));
        $message = json_decode($exception->getMessage());
        $code = method_exists($exception, 'getStatusCode') ? $exception->getStatusCode() : $exception->getCode();
        if(App::environment('production') && in_array($code, Handler::$HANDLED_CODES)){
            if($request->expectsJson()){
                $error = [
                    'error' => $code,
                    'message' => $exception->getMessage(),
                ];
                return  response()->json($error, $code);
            } else {
                return response()->view("errors.custom", [
                    'code'=> $code,
                    'message'=> __("error/codes.$code"),
                ], $code);
            }
        }
        return parent::render($request, $e);
    }
}

And what is causing the error is adding the return type to the method, since the parent is responding with \Symfony\Component\HttpFoundation\Response and my method expects Illuminate\Http\Response looks like an error is triggered and the response is somewhere converted to string.

Adding \Symfony\Component\HttpFoundation\Response to the return on my method fixed the problem.

public function render($request, Throwable $e):Response|JsonResponse|\Symfony\Component\HttpFoundation\Response {}