I have an app that uses the Storefront API and uses the createCart mutation to build an authenticated cart with the buyerIdentity (customer access token) provided.
I retrieve the checkoutUrl and load it into a desktop browser and navigate to my app user’s storefront liquid site. This flow used to be able to keep my user logged in, however something seems to have changed within the last 24 hours where my user is no longer logged in after loading the checkout url.
Additionally, if the user is already logged and then they load the checkout url, they get logged out. I’m wondering if anyone else has seen similar issues in the last few days or if it may be related to the new checkout system rolling out this month?
Yes, this is a known issue, and you’re correct that it’s caused by Shopify’s new one-page checkout rollout.
The absolute checkoutUrl you get from the Storefront API is no longer reliable for maintaining login sessions; because the storefront and checkout environments are now decoupled, it creates a session conflict that can log users out.
The recommended fix is to shift your logic to the client-side. Ensure the user is authenticated on the storefront first, then manage all cart mutations (like cartLinesAdd) using JavaScript in the browser.
When it’s time to pay, simply redirect to your store’s relative /checkout path. This allows the authenticated storefront session to correctly hand off the cart and user data to the new checkout system, preserving their login state.
This sounds like it may be connected to recent changes Shopify is rolling out with the new checkout system. The behavior you describe (users being logged out when navigating to the checkoutUrl) wasn’t happening before, but a few others have reported similar issues recently.
A few things you could try:
Confirm token handling – Make sure your customerAccessToken is still valid and that you’re passing it correctly in the buyerIdentity when creating the cart.
Check rollout status – Shopify has been progressively moving stores to the new checkout extensibility framework, and session handling/cookies can behave differently.
Contact Partner Support – Since this looks like a platform-level change, the safest path is to raise a ticket with Shopify Partner Support (or through your Partner Dashboard) with details of your request/response flow so they can confirm if this is expected.
You’re definitely not alone here — looks like a recent change on Shopify’s side rather than your implementation.
+1 to this - we are facing the exact same issue, and a bunch of our customers have contacted us about it breaking as of yesterday. We have yet to find any workable solution to this. It feels like a big and sudden regression to how this functionality worked with 0 warning.
We are trying to escalate this via partner support.