MissingCredentialsException always thrown if no credentials in `.env`

[AndyWendt]

since we register all Providers but don’t have any credentials in the .env file we always get an MissingCredentialsException [10:46] so we probably need to catch that in the Handler and ignore it or something like that

[danbovey]

Was about to submit some sort of PR to get around MissingConfigException because I don't have the Redirect URI in my .env, but it could be fixed at the same time as this. If you're going to fully support dynamically setting variables through Config, there should be a way to omit having to put bogus variables in the .env that I'm going to overwrite. Somehow...

[AndyWendt]

@danbovey I'll have to look into this. I believe that Laravel Socialite requires the credentials to be there so I may have to spoof them

[approached]

Hi @AndyWendt ,
the quick workaround is like this (default value):

    'facebook' => [
        'client_id' => env('FACEBOOK_API_ID', ''),
        'client_secret' => env('FACEBOOK_API_SECRET', ''),
        'redirect' => env('FACEBOOK_REDIRECT_URL', ''),
    ],

But this package has a main structure error. On every request you load many provider that you don't need it. A https://laravel.com/docs/5.0/container solution would be better.

protected $listen = [
    \SocialiteProviders\Manager\SocialiteWasCalled::class => [
        // add your listeners (aka providers) here
        'SocialiteProviders\Cheddar\CheddarExtendSocialite@handle',
    ],
];

Stackerror:

1) NewsroomActivityLogTest::it_shows_a_list_of_logs
InvalidArgumentException: Missing client credentials key [identifier] from options.

/vagrant/IALaravel/vendor/league/oauth1-client/src/Client/Server/Server.php:384
/vagrant/IALaravel/vendor/league/oauth1-client/src/Client/Server/Server.php:63
/vagrant/IALaravel/vendor/socialiteproviders/manager/src/SocialiteWasCalled.php:97
/vagrant/IALaravel/vendor/socialiteproviders/manager/src/SocialiteWasCalled.php:72
/vagrant/IALaravel/vendor/socialiteproviders/manager/src/SocialiteWasCalled.php:48
/vagrant/IALaravel/vendor/socialiteproviders/twitter/src/TwitterExtendSocialite.php:15
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:347
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Events/Dispatcher.php:221
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php:355
/vagrant/IALaravel/vendor/socialiteproviders/manager/src/ServiceProvider.php:15
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Container/Container.php:507
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:734
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:546
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:648
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:628
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Application.php:604
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:214
/vagrant/IALaravel/tests/TestCase.php:54
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Testing/ApplicationTrait.php:34
/vagrant/IALaravel/vendor/laravel/framework/src/Illuminate/Foundation/Testing/TestCase.php:36
/vagrant/IALaravel/tests/TestCase.php:25
/vagrant/IALaravel/tests/integration/Newsroom/NewsroomActivityLogTest.php:12

[AndyWendt]

@approached It is not a structural error. It is what extends the Socialite Facade.

[faustbrian]

4cc05ae

The config values will now be spoofed in order to support SocialiteProviders\Manager\Config properly without having to use dummy values in the .env file.