-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cart is null in response to "GetCartQuery" #1695
Comments
@MUlasevich - I was also running into that issue. Did you try using a customer impersonation token instead? |
@jtoromats i'm also having the same issue, using customer impersonation token
so it's not a solution either. With
Tried to create new V2/V3 API token with all possible permissions, but the result is the same, is there any solution for this? |
Hey @mhuretski, Customer Access Tokens will only be returned when using a Storefront Token instead of a Customer Impersonation token: https://developer.bigcommerce.com/docs/start/authentication/graphql-storefront#customer-access-tokens You should be able to run |
Hey @chanceaclark yes, I've created catalyst sales channel with I've tested it on a new store, on a brand new bigcommerce store everything works fine. Issue seems to be connected with existing stores created before new api was released or having some specific store settings preventing new api from working correctly. I've tested it on 2 existing stores and I'm getting cart null there. Should I create a ticket to customer support on this or perhaps there is some migration guide I missed for existing stores? |
Describe the bug
After adding item to cart, cart is always null in response to "GetCartQuery", both for guest and logged in user .
Also, every add to cart action results in new cart being created.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User is able to see cart items and proceed to checkout
Screenshots
Additional context
Was able to reproduce the same issue using several different BigCommerce stores
The text was updated successfully, but these errors were encountered: