Call to a member function make() on null

[UtkuDalmaz]

Laravel Version

12.40.2

PHP Version

8.4.15

Database Driver & Version

No response

Description

After I upgraded to Laravel version 12.40.2 I started getting

> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

   Error 

  Call to a member function make() on null

  at vendor/laravel/framework/src/Illuminate/Console/Command.php:171
    167▕      */
    168▕     #[\Override]
    169▕     public function run(InputInterface $input, OutputInterface $output): int
    170▕     {
  ➜ 171▕         $this->output = $output instanceof OutputStyle ? $output : $this->laravel->make(
    172▕             OutputStyle::class, ['input' => $input, 'output' => $output]
    173▕         );
    174▕ 
    175▕         $this->components = $this->laravel->make(Factory::class, ['output' => $this->output]);

      +4 vendor frames 

  5   artisan:35
      Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

Downgrading to 12.40.0 fixed the issue

Steps To Reproduce

composer install

[MuhammadHarisKhalil]

but this is not solution

[crynobone]

Hey there, thanks for reporting this issue.

We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here?

Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.

laravel new bug-report --github="--public"

Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.

Thanks!

[Sho0terInfo]

Has same issue on "laravel/framework": "12.37." after Symfony dependencies have been updated v7.3.6 => v7.4.0
Temporary fix for me: override laravel's symfony/console dependecy in project's composer.json by "symfony/console": "7.3."
It seems that the framework needs to hard-limit the Symfony dependency version to 7.3, as its latest release of version 7.4 broke a lot of things in Laravel, from critical errors to deprecation messages like #57962

[prince-noman]

Investigation Results

@crynobone, I have tested this on a clean Laravel 12.40.2 installation with Symfony Console 7.4.

To verify the behavior, I have executed both the Composer-driven execution path and the direct Artisan commands:

• composer install
• composer dump-autoload
• php artisan package:discover --ansi ← tested directly
• php artisan test
• And the post-autoload-dump script that automatically runs artisan package:discover

Everything worked normally on my setup.

Here is the output from my tests:

Composer-driven execution

Command:

composer test --testsuite=Console

Output:

@php artisan config:clear --ansi

INFO  Configuration cache cleared successfully.

@php artisan test

PASS  Tests\Unit\ExampleTest
✓ that true is true

PASS  Tests\Feature\ExampleTest
✓ the application returns a successful response  0.12s

Tests:    2 passed (2 assertions)
Duration: 0.22s

---

Direct Artisan execution

Command:

php artisan test

Output:

PASS  Tests\Unit\ExampleTest
✓ that true is true

PASS  Tests\Feature\ExampleTest
✓ the application returns a successful response  0.10s

Tests:    2 passed (2 assertions)
Duration: 0.20s

I could not reproduce the:

Call to a member function make() on null
vendor/laravel/framework/src/Illuminate/Console/Command.php:171

So at least on a fresh install, both the Composer script environment (post-autoload-dump → package:discover) and direct Artisan execution are working fine.

It may be environment- or project-specific.

A minimal reproducible repository from the original reporter would help investigate further.

[Sho0terInfo]

After further research I found out that there is a commit that fixes this issue: 8f47a31

So in my case the problem is that I have fixed the Laravel version to 12.37.* in my composer.json, which does not limit the version of its Symfony dependencies, but does not contain a commit that implements support for the latest version of Symfony. After updating Laravel to 12.38 or newer the error disappeared.

This does not answer the question of why the topic starter got this error on the current version of Laravel, but it will certainly be encountered by everyone who has setup a version of the framework to 12.37.* or lower in their composer.json, since the version of Symfony in its dependencies will continue to be updated beyond the supported version.

In my opinion, it would be good to reconsider the policy for designating framework dependencies versions in its composer.json.

[crynobone]

@Sho0terInfo that's why I asked for reproduction repository from the issuer.

As for you, locking the framework to specific version is your choice to exclude your project from receiving bug fixes such as above. The only solution is to upgrade to latest version.

[fulopattila122]

I also have this issue in a strange constellation of PHP/Laravel versions,
see this job run: https://github.com/vanilophp/framework/actions/runs/19704190462/job/56640547864

All the jobs that fail are causing the same error at the same location.

The rest of the tests are passing, so it could still be project-specific; however, this is a basic smoke test that has been successfully passing since 2017-10-01, so I suspect there's a dependency-related cause.

I'll investigate and come back if I find anything.

[fulopattila122]

Here's a summary of package versions:

#	PHP	Laravel	Symfony Console	Passes
1	8.3	11.44	7.3.6	✔
2	8.3	11.46	7.3.6	✔
3	8.3	12.2	7.3.6	✔
4	8.3	12.38	7.3.6	✔
5	8.4	11.44	7.3.6	✔
6	8.4	11.46	7.3.6	✔
7	8.4	12.2	7.4.0	❌
8	8.4	12.38	7.3.6	✔
9	8.5	11.44	7.4.0	❌
10	8.5	11.46	7.4.0	✔
11	8.5	12.2	7.4.0	❌
12	8.5	12.38	7.4.0	✔

It's interesting because even with v7.4.0 of Symfony Console, the error is not present when paired with Laravel 11.46 or 12.38

[fulopattila122]

I've made a curious testing with more laravel framework versions:

Laravel	Passes
11.44.7 - 11.46.1	❌
11.46.2 - 11.47.0	✔
12.0.1 - 12.37.0	❌
12.38.0 - 12.40.2	✔

So far as I can see, v12.40.2 is also unaffected!

I've found the common part in both versions:

v12.37.0...v12.38.0#diff-8d99b37ade8488d8eb389dd96a6399a4e70b19bf1b838536421b58393ee2fafa

v11.46.1...v11.46.2#diff-8d99b37ade8488d8eb389dd96a6399a4e70b19bf1b838536421b58393ee2fafa

So this is the Laravel code that solved the problem:

I'm not yet sure what to do with it 😅

[nwehrhan]

We have a compatibility pipeline that is failing with this issue as well.

laravel/framework (v11.46.1)
PHP 8.3.28
symfony/console (v6.2.1)

[MattyRad]

One method to reproduce (PHP 8.3):

composer create-project laravel/laravel:^10.0 deleteme

I'm targeting 10.x because composer create-project ... was removed after Laravel 10.x? Manually update the composer.json:

    "require": {
        "php": "^8.1",
        "guzzlehttp/guzzle": "^7.2",
        "laravel/framework": "11.46.1",
        "laravel/sanctum": "*",
        "laravel/tinker": "^2.8"
    },
    "require-dev": {
        "phpunit/phpunit": "^10.1"
    },

composer update

Result:

Executing command (CWD): '/usr/bin/php8.3' -d allow_url_fopen='1' -d disable_functions='' -d memory_limit='-1' artisan package:discover --ansi

In Command.php line 173:
                                            
  [Error]                                   
  Call to a member function make() on null