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've setup a hydrogen storefront with the new customer account API enabled. I'm running into an issue with the customer token and the cart handler. It seems like the token from the customerAccount doesn't work with the Cart Handler and I'm trying to figure out if there is another way to handle this.
I came across this comment in the CA API RFC which seems to confirm the issue.
I'm trying to use or implement the CountrySelector component but I receive an error from the API { "message": "Customer is invalid", "field": [ "buyerIdentity", "customerAccessToken" ], "code": "INVALID" } when trying to update the buyer identity.
I also have such problem type. I am getting customerAccessToken from CA API and want to use it to get details about Order using Storefront API (CA Order query it too limited with data and I can't receive detailed info about my product).
So on my local I receive customerAccessToken in next way: const customerAccessToken = await customerAccount.getAccessToken();
After I passed it to Storefront Order query, but as a result I receive: {customer: null}
I've setup a hydrogen storefront with the new customer account API enabled. I'm running into an issue with the customer token and the cart handler. It seems like the token from the customerAccount doesn't work with the Cart Handler and I'm trying to figure out if there is another way to handle this.
I came across this comment in the CA API RFC which seems to confirm the issue.
I'm trying to use or implement the CountrySelector component but I receive an error from the API
{ "message": "Customer is invalid", "field": [ "buyerIdentity", "customerAccessToken" ], "code": "INVALID" }
when trying to update the buyer identity.Any help with this would be greatly appreciated.
Originally posted by @NickHazen in #2493
The text was updated successfully, but these errors were encountered: