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
Symfony\Component\ErrorHandler\Error\FatalError: During inheritance of JsonSerializable: Uncaught ErrorException: Return type of League\OAuth2\Client\Token\AccessTokenInterface::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /Users/afaq/Documents/salla/dsjkgh/vendor/league/oauth2-client/src/Token/AccessTokenInterface.php:71
After adding #[\ReturnTypeWillChange] attribute before this function and now the issue error disappears but another issue occurs League\OAuth2\Client\Provider\Exception\IdentityProviderException: Please provide a valid authorization token in file /Users/afaq/Documents/salla/dsjkgh/vendor/salla/ouath2-merchant/src/Provider/Salla.php on line 88
and I think the cause of it is the serialization type
The text was updated successfully, but these errors were encountered:
Symfony\Component\ErrorHandler\Error\FatalError: During inheritance of JsonSerializable: Uncaught ErrorException: Return type of League\OAuth2\Client\Token\AccessTokenInterface::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /Users/afaq/Documents/salla/dsjkgh/vendor/league/oauth2-client/src/Token/AccessTokenInterface.php:71
After adding #[\ReturnTypeWillChange] attribute before this function and now the issue error disappears but another issue occurs
League\OAuth2\Client\Provider\Exception\IdentityProviderException: Please provide a valid authorization token in file /Users/afaq/Documents/salla/dsjkgh/vendor/salla/ouath2-merchant/src/Provider/Salla.php on line 88
and I think the cause of it is the serialization type
The text was updated successfully, but these errors were encountered: