lumen-framework: 'ReflectionException' with message 'Class path.storage does not exist'

In my case (lumen 5.3.3) got fixed by adding following lines right after $app definition in bootstrap/app.php file:

$app = new Laravel\Lumen\Application(
        realpath(__DIR__ . '/../')
);

$app->instance('path.config', app()->basePath() . DIRECTORY_SEPARATOR . 'config');
$app->instance('path.storage', app()->basePath() . DIRECTORY_SEPARATOR . 'storage');

//$app->withFacades();
$app->withEloquent();

This is happening because Illuminate’s helpers are being loaded before Lumen’s.

My autoload_files.php:

'f0906e6318348a765ffb6eb24e0d0938' => $vendorDir . '/laravel/framework/src/Illuminate/Foundation/helpers.php',
'bee9632da3ca00a99623b9c35d0c4f8b' => $vendorDir . '/laravel/lumen-framework/src/helpers.php',

This seems to happen when laravel/framework gets required by something, composer wipes out lumens vendor/illuminate files with vendor/laravel/framework (laravel/framework composer.json says replace illuminate.) - this in turn includes illuminate/Foundation/helpers.php

What’s weirder is it seems like we’re beholden to composer and how it scores/sorts autoload_files.php. I managed to get this to load in different (working) orders but I’m not 100% sure how - and frankly don’t have time for this. But that does confirm @bthibault’s issue.

This issue also persists after removing offending packages from composer.json and running composer update. I suspect this is a caching problem with the laravel replace and composer.

These steps seem to fix the issue, at least intermittently: (and may help reproducing the issue!)

1. Deleting your composer cache (rm -rf ~/.composer/cache/laravel/framework),
2. Delete your composer.lock file (not 100% this is required)
3. Delete your vendor dir (don’t worry it mostly gets reloaded from cache)
4. Run composer update

This issue still exists in 5.7

If you are running lumen and if any required package uses as a dependency laravel/framework it will fail.

Looks like it’s due to asamaru7/eloquent-model-generator-for-lumen.

Consider where storage_path() is being called from. In my case, it was called from the app’s config file, which was too soon. Moving the call into the app proper fixed this issue for me.

Swagger laravel has separate version for lumen https://github.com/DarkaOnLine/SwaggerLume

So I downloaded this version and all fine now

This helped me Thanks

Yeah, I also encountered the same problem now.

Lumen 8.x ,there are two storage_path helper functions shown below.

I used composer why laravel/framework, found appstract/laravel-opcache，removed it compsoer remove appstract/laravel-opcache (rm -rf vendor/ & composer install) or set path.storage in bootstrap\app.php => https://github.com/laravel/lumen-framework/issues/504#issuecomment-269410657

Try this:

$app->instance(‘path.config’, app()->getConfigurationPath()); $app->instance(‘path.storage’, app()->storagePath());

Make sure the call to parent::tearDown() is after your own code - the inverse of setUp().

    public function tearDown(): void
    {
        //////////////////////////////
        // Your code should go here //
        //////////////////////////////
        parent::tearDown();
    }