Deprecated cartDiscountCodesUpdate (missing discountCodes) attributed to our app — but our code never calls it. How to identify the source store?

@Wes-Dev-Shopify
@Donal-Shopify

An update from STOQ on the unsupported-app banner.

We just received a response from Developer Support regarding this issue. Developer Support traced part of our flagged traffic to a query called StoqSettings on Storefront API 2025-07. Their view: since the query is consistent across hundreds of shops, they can’t treat it all as third-party use, so the notice stays while deprecated requests attributed to the app are still detected.

StoqSettings was ours. It was inlined in our theme app extension’s app embed, and we changed the version from 2025-07 to 2026-07 around 9 September (v583) and we replaced it completely in the version we released around 23 September (v590). Current STOQ code (v600) makes no 2025-07 calls. It’s still being called because Shopify keeps serving storefront HTML rendered by older versions of our app embed:

  • In the last 24 hours, ~830 shops served our app-embed HTML from the 2025-07 builds. That HTML was rendered between late June and early September, with a median age of ~49 days.
  • Another ~1,165 shops served HTML from the builds after that, which still had the old query but were on the new 2026-07 version.
  • The oldest actively running version is v525 which is 4 months old.
  • This was tracked using the Shopify Pixel, we have all events sent by the Pixel also carry the current theme app extension version.
  • Because the code is in the rendered page, every buyer who gets one of those cached pages runs the old request, even though the app embed was updated weeks ago.

We can’t invalidate those renders. Updating the app extension doesn’t refresh them, and there’s no API to trigger it. So with theme app extensions, “deprecated calls attributed to the app” will include our own superseded code for weeks or months after we ship a fix. That’s on top of third-party reuse of the public token, which we can’t control either.

Enforcing on that signal means penalising an app that has already shipped the fix. Could Shopify either:

  • invalidate cached app-embed renders when an app releases a new extension version, or
  • base the unsupported status on what the current app version calls, not on traffic from stale cached pages?

I think enforcing it at all doesn’t make sense given what it is but I am sure we can come to some compromise.

Hoping for a speedy solution!

@Wes-Dev-Shopify, please provide an update ASAP.

We’re seeing the misleading error banner in our app(s) now too, even though @Donal-Shopify said this would not happen…

Same with our apps. We are seeing a huge drop in installs because of this and confused merchants.

Are there any updates? My app is experiencing the same issue.

Hey folks - we’ve investigated the reports here and confirmed that some cartDiscountCodesUpdate deprecation alerts were false positives. We also found calls that need to be updated for compatibility with newer Storefront API versions.

What we’ve done:

  • Temporarily suppressed the related “This app is unsupported” warnings for the affected public apps we identified, both during installation and in the merchant’s Admin Apps list.
  • Rolled out a fix so these calls are no longer incorrectly flagged. Existing Dev Dashboard alerts for those calls should clear in about three days.

Please continue reviewing your app for deprecated API calls. If your app calls cartDiscountCodesUpdate, check every place it’s used and migrate those calls to Storefront API version 2026-01 or later. If you pass discountCodes through a GraphQL variable, declare that variable as [String!]!. The nullable declaration [String!] fails validation on 2026-01 even when you supply a value.

Our app is also showing the “This app is unsupported” banner during installation, and it’s already affecting our merchant installs. We’ve been in touch with the Shopify Support team about this issue and are still waiting for an update! We’d really appreciate a quick resolution to this issue.

@Wes-Dev-Shopify Hello, a customer told me that when installing my app, it displayed “This app is unsupported,” and my app installation rate has dropped significantly in the last two weeks. I suspect this is the cause. Please investigate this issue as soon as possible.

We’re seeing the same issue. The Dev Dashboard flagged CartDiscountCodesUpdate.discountCodes (last detected Oct 3, 2026), but our app doesn’t call this mutation.

Thanks @Wes-Dev-Shopify for the fix. We’ll check whether the alert clears in the next few days and follow up here if it doesn’t.

@Wes-Dev-Shopify the banner has started displaying again for one of our apps (183860363265), could you please disable that banner until this is figured out?

This is heavily impacting our install rate and ranking.

We still see the same issue (app ID 2525233). The Dev Dashboard is flagging cartDiscountCodesUpdate.discountCodes and “This app is unsupported” is also displayed to merchants. @Wes-Dev-Shopify @Donal-Shopify, could you please fix it for us as well?

Hey folks - we’re continuing to work on this and are doing our best to mitigate the impact for everyone affected. We’ve extended the temporary suppression of the related “This app is unsupported” warnings to more affected apps today including the two mentioned in the reports above.

For the time being, the Dev Dashboard alerts remain visible and should clear about three days after the date of the last detected call shown in your dashboard.

If you’re still seeing the merchant-facing warning, please share your app ID so we can check your app specifically. If you’d prefer to share those details privately, let me know and I can set up a DM.