Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guzzle Object could not be converted to string #70

Closed
duncan-qabana opened this issue Sep 8, 2016 · 1 comment
Closed

Guzzle Object could not be converted to string #70

duncan-qabana opened this issue Sep 8, 2016 · 1 comment

Comments

@duncan-qabana
Copy link

I have used this library for some months now. Since 2 days, I am getting errors when connecting to Exact.
The first is:
Fatal error: Uncaught exception 'Exception' with message 'Could not connect to Exact: Client error: 'POST https://start.exactonline.nl/api/oauth2/token' resulted in a '400 Bad Request' response: 'Bad Request' in /vagrant/valvomo/include/application/class.Exact.php:901 Stack trace: #0 /vagrant/valvomo/include/application/class.Exact.php(40): Exact->connect(Array) #1 /vagrant/mijn/index.php(1040): Exact->index('10', Array) #2 {main} thrown in /vagrant/valvomo/include/application/class.Exact.php on line 901

After some debugging, I found:
Catchable fatal error: Object of class GuzzleHttp\Client could not be converted to string in /vagrant/vendor/picqer/exact-php-client/src/Picqer/Financials/Exact/Connection.php on line 114

But I have no clue how to fix it, going deeper is going into the src code of Guzzlehttp. Do you have a fix?

@duncan-qabana
Copy link
Author

Never mind, somehow the old keys were cached and weren't pulled from the storage. Chaos ensued.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant