You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm encountering an issue when passing a custom GuzzleHttp\Client instance as the authenticationClient parameter in SellingPartnerApi::seller(). According to the documentation, this parameter should accept a GuzzleHttp\Client, but when provided, it results in the following error:
Error:
Typed property Saloon\Http\Senders\GuzzleSender::$client must not be accessed before initialization.
Code
Steps to Reproduce
Instantiate a GuzzleHttp\Client with a proxy
Additional Information
PHP: 8.4.1
Selling Partner API SDK: 7.2.4 (jlevers/selling-partner-api)
Guzzle: 7.9.2
Laravel: 11.41.3
I've confirmed that the issue persists even when using a clean GuzzleHttp\Client instance without additional configuration.
Is there an internal constraint preventing the use of a custom GuzzleHttp\Client, or is there a required initialization step that is missing? Any guidance would be appreciated.
The text was updated successfully, but these errors were encountered:
Problem description:
I'm encountering an issue when passing a custom GuzzleHttp\Client instance as the authenticationClient parameter in SellingPartnerApi::seller(). According to the documentation, this parameter should accept a GuzzleHttp\Client, but when provided, it results in the following error:
Error:
Code
Steps to Reproduce
Instantiate a GuzzleHttp\Client with a proxy
Pass it to SellingPartnerApi::seller()
Attempt to make a request:
Additional Information
PHP: 8.4.1
Selling Partner API SDK: 7.2.4 (jlevers/selling-partner-api)
Guzzle: 7.9.2
Laravel: 11.41.3
I've confirmed that the issue persists even when using a clean GuzzleHttp\Client instance without additional configuration.
Is there an internal constraint preventing the use of a custom GuzzleHttp\Client, or is there a required initialization step that is missing? Any guidance would be appreciated.
The text was updated successfully, but these errors were encountered: