Laravel with App Engine Standard Class 'Facade\Ignition\IgnitionServiceProvider' not found

Question

This is driving me crazy second day. I'm new to Laravel and trying to get Laravel 6 work on Google App Engine Standard. Tried: This tutorial and other ones, but it still fails to load Laravel index page

What I have done:

Created new Laravel project
Checked that Laravel is working on local host with php artisan serve
Generated new key with php artisan key:generate --show
Created app.yaml file with:

runtime: php72

env_variables:
  APP_KEY: iktbUa2quYPV2av3zDx0XAuEVjwzVQY/oMfyI2PQNKk=
  APP_STORAGE: /tmp
  VIEW_COMPILED_PATH: /tmp
  SESSION_DRIVER: cookie

Modified bootstrap/app.php by adding $app->useStoragePath(env('APP_STORAGE', base_path() . '/storage'));
Rancomposer remove --dev beyondcode/laravel-dump-server
Also ran: php artisan cache:clear, php artisan route:cache, php artisan config:clear, php artisan view:clear (as other tutorials suggested)
And gcloud app deploy

And I get error: "Class 'Facade\Ignition\IgnitionServiceProvider' not found"

Did you registered your provider inside `config/app.php [provider & alias]` ? — Rashed Hasan, Sep 24 '19 at 19:49

score 47 · Answer 1 · answered Jun 05 '21 at 07:13

47

If you're facing this issue after upgrading composer 1.0 to 2.0. Then you can follow this step:

Go to the project directory
Run composer install
Run composer dump-autoload
Try to run php artisan serve It solved for me

answered Jun 05 '21 at 07:13

Abid Rakhmansyah

896
8
22

I upgraded from composer 1.x to composer 2.x so this issue was reported. your answer helped me. Thanks :) – Dinesh Suthar Jun 08 '21 at 08:21
1

It even works without step 3. Thank you – Ayenew Yihune Oct 06 '21 at 11:28
I have updated the PHP version and then got this error but it's solve after `composer install` – always-a-learner Jun 30 '22 at 10:21

score 9 · Answer 2 · answered Nov 23 '19 at 06:44

9

Please Try

composer dump-autoload

It solved for me

answered Nov 23 '19 at 06:44

Asadut Zaman

273
3
6

This broke my all application. – Krishna Karki Feb 25 '21 at 09:57
@KrishnaKarki This just ensures that your dependency files are properly getting discovered and loaded. It def shouldn't break your application, unless the dependencies themselves correctly break your application, or unless you have a discrepancy in your composer versions (i.e. installed the initial deps with composer v1, and installed new deps with v2, etc.) – Aaron Krauss Jul 19 '21 at 17:19
This helped out! Thank you so much. Any idea what just happened to understand this more technically? – Harry Sep 08 '22 at 11:19

score 8 · Answer 3 · answered Dec 17 '19 at 07:30

8

App engine install dependency with "--no-dev" flag. If your application is debug mode and there is an error application is try to render error page by "facade/ignition" packages.

Solve-1: You can move "facade/ignition" dependency from "require-dev" to "dev" in composer.json file

Solve-2: You can run as production environment and with false APP_DEBUG flag

answered Dec 17 '19 at 07:30

Ömer Kamçılı

101
1
3

Thank you this makes much more sens than other answers – Kwaadpepper May 23 '22 at 12:33

score 5 · Answer 4 · answered Sep 25 '19 at 18:24

I have experienced other errors as well, most of them gave me Error 500 and

nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /tmp/google-config/nginx.conf:3 in Stackdriver Logger

Also I was not aware that App Engine was executing composer.json on build (see Specifying Dependencies). And it seems the issue was that it cached that.

Everything was resolved by replacing command in step 7. :

gcloud app deploy with gcloud beta app deploy --no-cache

It seems that if I would have done all steps as in tutorial from the start I would not have any issues.

score 4 · Answer 5 · answered Sep 10 '21 at 04:36

4

I try composer update and its working fine

answered Sep 10 '21 at 04:36

Muhammad Azam

117
4

score 3 · Answer 6 · edited Nov 08 '19 at 13:58

3

Try

php artisan route:clear

and you're good to go.

edited Nov 08 '19 at 13:58

lczapski

4,026
3
16
32

answered Nov 08 '19 at 13:07

Chris

31
1

score 3 · Answer 7 · answered Sep 28 '21 at 12:51

3

Try running

composer update

or

composer dump-autoload

answered Sep 28 '21 at 12:51

hackernewbie

1,606
20
13

score 2 · Answer 8 · edited May 30 '22 at 17:38

2

Go to your project terminal and run :

composer install
composer dump-autoload
php artisan serve

And your problem will go away.

edited May 30 '22 at 17:38

Besworks

4,123
1
18
34

answered May 28 '22 at 10:49

Moris Kakengi

21
3

score 1 · Answer 9 · edited Apr 30 '22 at 20:39

1

I am also new to Laravel and I have experienced with this issue, and I searched solution which was

first run this command on your terminal

composer update

second run the command on below

composer dump-autoload

and then see the result :)

edited Apr 30 '22 at 20:39

Jaro

1,587
5
20
39

answered Apr 28 '22 at 13:09

yura yuriyev

11
2

In my case, I need run `composer dump-autoload` to use my helpers. It works for me… and update my laravel project from v7.28 to v7.30 ! – bcag2 Oct 19 '22 at 14:15

score 0 · Answer 10 · answered Jul 30 '22 at 09:37

0

just uncomment soduim line from your ini file

before

;extension=sodium

after

extension=sodium

answered Jul 30 '22 at 09:37

Hadayat Niazi

1,991
3
16
28

score -1 · Answer 11 · answered Apr 16 '21 at 15:15

-1

If you are facing this issue while running phpUnit tests then try to clear cache of bootstrap folder.

answered Apr 16 '21 at 15:15

Kapil Verma

178
3
17

Laravel with App Engine Standard Class 'Facade\Ignition\IgnitionServiceProvider' not found

11 Answers11

Linked