Target [Nexmo\Client\Credentials\CredentialsInterface] is not instantiable while building [Nexmo\Client]. about nexmo-laravel

[leandrit1]

I fixed my issue by running php artisan config:clear , it took me a bunch of time as I ran cache:clear and was not thinking of using config:clear.

[atapatel]

+1 i am also facing this issue.

[tjlytle]

@aliuwahab21 @atapatel see this related issue.

[leandrit1]

Hi @tjlytle , I am having the same problem, and furthermore I have noticed that the nexmo.php even though I followed all the steps, when I run php artisan vendor:publish the nexmo.php file can not be found on the config/nexmo.php as we see it in some tutorials but we find it just in the vendor/nexmo/laravel/config/nexmo.php

Target [Nexmo\Client\Credentials\CredentialsInterface] is not instantiable while building [Nexmo\Client].

[tjlytle]

@LeandritGo What version of Laravel are you using?

[leandrit1]

Laravel 5.3 On 27 Mar 2017 18:10, "Tim Lytle" <[email protected]> wrote: @LeandritGo <https://github.com/LeandritGo> What version of Laravel are you using? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXrR6EeAGQWhVgj2xwVaJaeHE0Nu2zDvks5rp9-NgaJpZM4LKUvb> .

[leandrit1]

Are there any news regarding the issue?

[tjlytle]

@LeandritGo I can't replicate, but if it's not creating config/nexmo.php just copy the file from vendor/nexmo/laravel/config/nexmo.php to your config directory.

And if artisan vendor:publish isn't creating the config file, seems like there's something missing in your config/app.php (Laravel doesn't know about the Nexmo Service Provider).

[tjlytle]

@afolson See @enasellithy's comment in the closed thread (#3). I can't replicate unless I drop the client from the providers config. Any ideas? I'm sure there could be better error handling as well.

[afolson]

I tried just now and was unable to reproduce on L5.3 or L5.4 unless I dropped the client from the providers array in config/app.php. Additionally, I was able to verify that artisan vendor:publish puts a nexmo.php file in the config directory.

It seems like people are using various versions of the Laravel package AND the client, or possibly just using nexmo/client instead of nexmo/laravel. Would someone mind running composer update nexmo/laravel and making sure that "nexmo/laravel": "^0.4.0" appears in composer.json and that you see a block similar to this in composer.lock:

Note that nexmo/laravel is pulling in nexmo/client and they have the same version number here. In theory, adding/removing packages via composer should re-generate the autoload file, but for good measure you may want to run composer dump-auto just in case.

If it's still not working after all of that we can debug deeper 🐛

[tjlytle]

@afolson Wonder if there's a way to catch that (including nexmo/client but trying to invoke using the service provider, and provide a better error message.

[mheap]

As we've not been able to reproduce this, I'm going to close the issue. We can link and reopen in future if required.

[erickbrz]

solved for me, i had in my config/nexmo.php ('signature_secret' => xxxxxx), after deleted the line, send sms!