Our dashboard says we have until April 1 to migrate, but I’ve seen February in emails from Shopify. Which is it?
The main barrier to us migrating is the lack of the inventoryItem field on the variants of the productSet mutation. I saw in another thread that you are planning to add this, but not sure if that will be done by Feb 1.
What happens if we aren’t migrated?
Hi, inventoryItem has been added
Hey SethT,
As @Luke mentioned above inventoryItem has been added - so hopefully you’re unblocked fully.
For public apps (on the Shopify App Store) the deadline for migration is Feb 1st, and for custom apps (not on the App Store), the deadline is April 1st.
If you don’t migrate by this time, the apps won’t “break” but merchants who start using the increased variants feature, won’t be able to use it in the context of the app - and they’ll see warnings on their admin about your app. More info on this here: New GraphQL product APIs and early access to 2048 (aka 2K) variants
@Liam-Shopify Is there any reason the warning to migrate by Feb 1st has disappeared from the app health dashboard? Definitely confusing if the deadline is still Feb 1.
Hi Rares,
We had to make some changes to our tracking of API calls in order to prevent merchants from receiving “unsupported” notifications for unmigrated apps. This temporarily removed the notifications from the API health dashboard as well – they should back very soon however.
Hi Liam @Liam-Shopify,
I hope you’re doing well.
The alert disappeared from my Partner Dashboard about a week ago, but it has just reappeared. It’s been quite frustrating as I migrated everything several weeks ago, and now the alert is showing up again.
Could this be a Shopify issue? If not, I’m unsure where to look for the problem.
I’d really appreciate your help with this.
Thank you in advance!
The erroneous “unsupported” label has been a problem ever since it was introduced.
A functioning API response against an endpoint whose EOL is X weeks away does not mean the app is “unsupported”. It means it’s working!
Your label is inaccurate and leads to consumer confusion. Ever since it was introduced we’ve received emails asking when our app will be “supported”, even though it’s always been supported and has never not worked.
Additionally, you do not expose any information about what made the call IP, parameters, user agent —nothing.
This is absolutely frustrating…
Despite migrating to a “supported” API version several weeks ago, the deprecated call alert still appears every day at 12:00 AM (???). Unfortunately, no additional information is provided in the message to help pinpoint the source of the issue.
I’ve spent several days meticulously reviewing every line of code in the app, but I haven’t been able to identify where the deprecated call is originating.
I have sent a couple of emails to Shopify… no replies… write in forums to Shopify team… no replies…
This is absolutely annoying and frustrating!.
Same here, @BigVan. The API call deprecation notice has popped up again, and I honestly have no idea why. I’ve gone through my code multiple times, and everything seems fine, so this is really frustrating. I’m worried about how this will affect our reputation, especially since the deprecation notice makes it look like the app is unsupported to merchants.
Getting the notification just 4 days before the deadline, combined with the deprecating API monitoring disappearing from the Partner Dashboard, has turned this into an unnecessary panic situation.
I’ll add my voice to the chorus of frustration here - we have also fully migrated our apps, and one of our apps is now suddenly showing the deprecation warning. Removing warnings from the API health dashboard with no notice and then bringing them back less than a week before the deadline is mind-boggling.
@Liam-Shopify as others seem to be getting false positives, is it possible that the alerting isn’t accurate? Or if we’re seeing that banner, is our app definitely going to be delisted on Feb 1?
This deprecated API call banner also appears on our side. We moved all of our REST APIs to GraphQL several days ago. We are working hard to meet all of your requirements, but it is very frustrating to see this banner, knowing that we have already made the necessary changes.
Please double-check your API health system.
It seems obvious that there is something wrong with the API health system.
It is doubly frustrating to see the message with a countdown of only 4 days and still not have any response from the Shopify team.
At the very least, there should be a message to reassure all developers which has reported the issue. 
Hello @Jason_Freeman @Levente_Kovacs, Were you able to resolve the issue? Do you have any updates from Shopify?
The message has appeared again today, and I still haven’t received a response to the case I opened five days ago or any information from the forum.
I keep reviewing my code over and over, but I can’t find where the problem is. This is taking a toll on my health.
Same here 
No, I don’t have any feedback from Shopify as usual.
I’ve opened a support ticket. In the past, we’ve been able to get more information from support on deprecated API calls - in every other case, it’s been someone on the team accidentally using a deprecated API version for a one-off API call, and Shopify support has been able to provide detailed data on the unsupported calls.
Hopefully I will get some information there (as support’s initial response was unhelpful) or @Liam-Shopify will be able to add more info here!
DMing folks now to dig into this
Hey everyone,
Let me ask, are there any updates here?
Hi Levente,
I’ve been checking our reports to see which calls were made that would be triggering these messages. I’ve just DMed you for more info.
I have replied to you in DM. Thank you
@Liam-Shopify , would you be able to help us as well? We’re in the same boat as folks here. Could you help identify the unsupported API calls if any? Thanks heaps!
Has anyone found a solution to this problem?