Open asacarter opened 2 years ago
There seems to be an issue where some users logging in with per-ser via Rest don't get a session.
I'm still trying to figure it out.
Osiset\BasicShopifyAPI\ResponseAccess Object ( [container] => Array ( [access_token] => shpat_ba77093f97341f31f76167d9524***** [scope] => write_orders,read_products,read_inventory,write_assigned_fulfillment_orders,write_merchant_managed_fulfillment_orders [expires_in] => 86398 [associated_user_scope] => write_orders,read_products,read_inventory,write_assigned_fulfillment_orders,write_merchant_managed_fulfillment_orders [session] => [account_number] => [associated_user] => Array ( [id] => 86370779**** [first_name] => **** [last_name] => **** [email] => contact@app***** [account_owner] => 1 [locale] => en-GB [collaborator] => [email_verified] => ) ) [position] => 0 )
The data seems to come from the access response from Shopify so not an issue with the library.
Anyone have any idea why in some instances Shopify grants access but does not provide a session or account number?
There seems to be an issue where some users logging in with per-ser via Rest don't get a session.
I'm still trying to figure it out.