Checkout opens without associated buyer identity

What area is the issue related to?

Checkout Sheet Kit

What platform does the issue affect?

All platforms

What version of @shopify/checkout-sheet-kit are you using?

3.2.0 - Multiple Devices

Do you have reproducible example code?

Yes, though it is not consistently reproducible.

// Function to regenerate the checkout URL
const cart = await cartBuyerIdentityUpdateLite({
  customerAccessToken,
  email,
  phone
});
const checkoutUrl = cart?.cart?.checkoutUrl;
return shopifyCheckout.presentCheckout(checkoutUrl);

// Helper to update buyer identity and get new checkout URL
export async function cartBuyerIdentityUpdateLite(input: {
  customerAccessToken: string;
  email?: string;
  phone?: string;
}) {
  const currentCart = appStorage()?.currentCart ?? {};
  if (currentCart.id && input.customerAccessToken) {
    const variables: CartBuyerIdentityUpdateMutationVariables = {
      lite: true,
      cartId: currentCart.id,
      buyerIdentity: {
        customerAccessToken: input.customerAccessToken,
        ...(input.email && { email: input.email }),
        ...(input.phone && { phone: input.phone }),
      },
    };
    const result = await runTanstackQueryMutation<
      CartBuyerIdentityUpdateMutation,
      CartBuyerIdentityUpdateMutationVariables
    >(CartBuyerIdentityUpdateDocument, variables, useCartBuyerIdentityUpdateMutation.getKey());

    return { cart: result?.cartBuyerIdentityUpdate?.cart };
  }
}

# GQL Mutation
mutation cartBuyerIdentityUpdate(
  $cartId: ID!,
  $buyerIdentity: CartBuyerIdentityInput!,
  $collectionsFirst: Int = 0,
  $lite: Boolean = false
) {
  cartBuyerIdentityUpdate(cartId: $cartId, buyerIdentity: $buyerIdentity) {
    cart {
      ...cartResponse @skip(if: $lite)
      checkoutUrl @include(if: $lite)
      id @include(if: $lite)
    }
    userErrors {
      ...cartError
    }
  }
}

Steps to Reproduce

• Run the app in a production environment (release build).
• Ensure a valid cart is present, with buyer identity added using cartBuyerIdentityUpdate.
• Call shopifyCheckout.presentCheckout(checkoutUrl).
• Occasionally, the opened checkout is missing the buyer identity, and the user is prompted to log in.

Expected Behavior

Checkout presented via Sheet Kit should respect the buyer identity, and the user should remain logged in within the checkout session.

Actual Behavior

Sporadically (and only in production builds), the Sheet Kit presents a checkout screen that:

• Does not reflect the authenticated buyer identity.
• Prompts the user to log in again (Within the checkout sheet webview), even though a valid customerAccessToken was passed to the mutation.
• This happens even though the cartBuyerIdentityUpdate mutation succeeds and returns a fresh URL.

Storefront domain

https://rforrabbit1.myshopify.com

Screenshots/Videos/Log output

rec.mov

• This issue could not be reproduced in development mode.
• Video recording attached shows a clear instance where:
  • A valid mutation is fired.
  • A new checkoutUrl is returned and passed to the Sheet Kit.
  • The resulting checkout still asks the user to log in.
• We suspect a timing/race issue, or internal caching behavior in the Sheet Kit or web checkout instance.
• No errors are returned from the mutation.

[kieran-osgood-shopify]

Hi @adithyan-apmkr,

To help us investigate further, could you please provide the following information?

1. Are you using preloading in CSK?
2. When you reproduce the issue, could you provide us the x-request-id header, This will allow us to trace the request and look for any anomalies.

We suspect there might be a race condition involved, some additional testing may highlight where.

If you could try the following changes:

• 3.1 Attach the buyerIdentity during the cartCreate call instead of in a separate buyerIdentityUpdate.
• 3.2 I'm unfamiliar with the skip instructions, would you try without that, and use defer to await the response.

Hi @kieran-osgood-shopify , thanks for following up.

• We are not using preloading in CSK — the checkout is loaded fresh each time.

• Unfortunately, the issue is intermittent and we haven’t been able to capture any request logs or x-request-id headers from affected sessions yet.

• Regarding buyer identity, we do attach it during the cartCreate call itself. The cartBuyerIdentityUpdate call is used additionally to ensure the checkoutUrl is up to date before presenting checkout.

• We're currently unable to reproduce the issue in development builds — it has only been observed in production/release environments.

We’re also exploring your suggestions:

• Looking into removing the @skip(if: $lite) directive in favor of @defer

Let us know if there’s anything else you’d like us to try on our end — we’re continuing to debug and will report back if we’re able to consistently reproduce the issue.

Hi @kieran-osgood-shopify ,

We were able to capture a request ID where the buyer identity association failed, attached it below

ID: 109bf362-71da-4947-8640-6e82775609b1-1752498792

[kieran-osgood-shopify]

@adithyan-apmkr Thanks for sharing - will see if I can find anything/anyone to look into this.
Ignore previous comment - I found the timestamp: Jul 14, 2025 – 2:13:13 pm.

Thanks

Hi @kieran-osgood-shopify ,

We've managed to capture some recordings where this issue occurs. In these cases, the request returns a success response, but the generated checkout URL does not have the user logged in-whether it's opened in a browser or within the webview.

Since the recordings contain some personal or sensitive information (like user tokens and related details), we're hesitant to share them publicly. Is there an email address or a secure channel we could use to share these recordings with you?

[kieran-osgood-shopify]

@adithyan-apmkr you can share them to my email: kieran.osgood@shopify.com

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in 30 days. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Please re-open it if it is still relevant.

[kieran-osgood-shopify]

@adithyan-apmkr I believe you were in contact with our support directly - should this issue remain open or have your issues been resolved?

[DT-Nineteen]

same issue today