Version 1.5 breaks laravel drivers

[MordiSacks]

I register a custom session driver in AppServiceProvider::boot

Session::extend('custom', function ($app) {
 // implementation....
});

on version 1.4.0 everything works as epxected
after upgrading to 1.5.0 or 1.5.1 the app breaks and throws an InvalidArgumentException
Driver [custom] not supported.

I have Isolated the issue to this specific package, by updating every single package individually

Environment (please complete the following information):

• PHP Version: 8.3.16
• OS: Debian 12
• Intervention Image Version: N/A
• GD or Imagick: N/A

[olivervogel]

This is strange. However, I cannot link this bug to intervention/image-laravel at the moment.

The main change in version 1.5 was that an HTTP response macro was registered in the service provider of this package.

It seems that this bug comes from Laravel itself. It always happens when you try to register any response macro before a custom session handler.

I get the same error when I modify a fresh Laravel 11 installation (without this package) with the following code in app/Providers/AppServiceProvider.php.

Please report this to Laravel.

namespace App\Providers;

use App\CustomSessionHandler;
use Illuminate\Support\Facades\Session;
use Illuminate\Support\ServiceProvider;
use Illuminate\Contracts\Foundation\Application;
use Illuminate\Support\Facades\Response;

class AppServiceProvider extends ServiceProvider
{
    /**
     * Register any application services.
     */
    public function register(): void
    {
        //
    }

    /**
     * Bootstrap any application services.
     */
    public function boot(): void
    {
        Response::macro('caps', function (string $value) {
            return Response::make(strtoupper($value));
        });

        Session::extend('custom', function (Application $app) {
            return new CustomSessionHandler();
        });
    }
}

[olivervogel]

I fixed this in 1.5.2 by postponing the registration of the macro until after all service providers have been fully loaded.

I think you can still report the issue from my previous comment to Laravel. ✅ Done

[MordiSacks]

Thank you :-)