Undefined constant GuzzleHttp\Client::VERSION #2442
-
Describe the bugPHP Fatal Error This just started happening today. Nothing (that I know of) had changed. I did upgrade from aws.3.198.2 to aws.3.220.3 AFTER the problem began, hoping that would resolve it. But it did not.
Expected BehaviorCorrectly get a list of files from an S3 service Current BehaviorPHP Fatal Error Reproduction StepsAll S3 operations seem to fail. Possible SolutionSome forums suggest GuzzleHttp\Client::VERSION is no longer supported, but the call stack makes it look like the GuzzleHttp\Client::VERSION reference is in Additional Information/Contextguzzlehttp/guzzle 7.4.2 SDK version usedaws.3.220.3 Environment details (Version of PHP (
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
I got this working by installing the AWS api via composer, and no longer using the straight php api. I would still recommend this be looked at - for folks using the php api and also have Guzzle installed via Composer. |
Beta Was this translation helpful? Give feedback.
-
Hi @SteveMullen, thank you for reaching out. I tried to reproduce the reported issue with the environment details that you provided and I was not able to, which indicates that the issue could be related with something else, maybe a conflict with different guzzle versions being load, or possibly there was a guzzle version locked down by the composer.lock file which would've required you to run "composer update"; You would've be able to check this by running "composer show guzzlehttp/guzzle" and this would've tell you the guzzle version that is being load, nonetheless I am glad you found a workaround. For now I will close this issue! Thank you! |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
Hi @SteveMullen, thank you for reaching out. I tried to reproduce the reported issue with the environment details that you provided and I was not able to, which indicates that the issue could be related with something else, maybe a conflict with different guzzle versions being load, or possibly there was a guzzle version locked down by the composer.lock file which would've required you to run "composer update"; You would've be able to check this by running "composer show guzzlehttp/guzzle" and this would've tell you the guzzle version that is being load, nonetheless I am glad you found a workaround.
For now I will close this issue!
Thank you!