"Update required for new Markets" warning - what replaces deprecated localization.market field?

Functions
1

Our users started seeing this warning on our app listing:

Update required for new Markets
The app developer needs to update this app to support new Markets. Contact the developer for assistance.

We’re trying to address it but the only deprecated field we use is localization.market.id - and there’s no documented replacement.

Discount function (run.graphql):

query RunInput {
  localization {
    language { isoCode }
    market { id }  # deprecated
  }
  # ...
}

The schema shows:
market: Market! @deprecated(reason: "This `market` field will be removed in a future version of the API.")

Our use case: Merchants can limit deals to specific markets. We need to know the buyer’s current market to filter which deals apply.

Questions:

  1. Is using this deprecated field causing the “Update required for new Markets” warning?
  2. What’s the recommended replacement for localization.market.id?

We’re on API version 2025-10.

Thanks!

4 Likes
2

The localization.market field in your Function input query is unlikely to be what’s causing the “Update required for new Markets” warning.

That warning is driven by Admin GraphQL API calls, not Function input queries. If your app makes any market-related Admin GraphQL calls, upgrading to API version 2025-04 or newer is what clears the warning.

As for the Function field deprecation itself, the closest available field is localization.country.isoCode:

query Input {
  localization {
    country {
      isoCode
    }
  }
}

Since markets are shop-defined and can contain multiple countries, there’s no direct replacement that returns a market ID. I’ll look into getting a proper replacement for localization.market added in a future API version.

1 Like
3

Ah, thats good to hear. For Admin API we’re on 2025-10 for months now. Also there’s no warning on dev platform (there’s one unrelated issue).

Screenshot 2026-04-14 at 07.59.41
Screenshot 2026-04-14 at 07.59.413424×884 200 KB

I wonder what could be causing the deprecation banner to appear then?

4

I’m not seeing calls earlier than 2025-10 from your app either. I’ll check internally if we’ve recently changed when/how warning is presented and get back to you.

1 Like
5

@dostu Apparently there were 2 unsafe API calls from your app around April 10th. Were you testing an older version of your app around that time by any chance?

6

By unsafe you mean with old API version right? Might have been AI while the team were debugging something :person_shrugging: Since it was two calls and the app actually functions well could you help us get the banners removed?

7

@dostu - we had a similar issue where an old API was called locally during debugging. If you haven’t already (naturally) re-deployed, it might be worth doing so, as we were told at the time that it kicks off some checks.

8

@bkspace thanks for sharing. We have made some deploys over the last few days already.

1 Like