It is showing this error on our Partner dashboard, how can we resolve this?
Shopify has detected that OUR_APP is using an older version of either the shopify_app gem or @Shopify_77 /koa-shopify-auth library that has called the deprecated Embedded App SDK (EASDK) within the last 10 days.
You must update this app to use either shopify_app v18.1.1 or @Shopify_77 /koa-shopify-auth v5.0.3. Updating will replace these EASDK calls with App Bridge.
Is your app server built using Rails or Node?
If it’s Rails, you’ll need to update the shopify_app gem.
If it’s Node, you’ll need to update the @Shopify/koa-shopify-auth library.
In both cases, updating to the latest version would resolve the issue.
Our app is built on laravel, what do you suggest for it?
Our app is built on laravel
That explains the confusion.
In terms of the technical cause, I replied on this GitHub issue in the laravel-shopify repo (an open-source repo, NOT maintained by Shopify).
We will make sure that apps in your situation (that do NOT use the EASDK API directly) will not get impacted. I am working with our partner managers on a clear message to clearly communicate this.
Hi Im using nodejs, You solved this issue??
Hi Joey,
We’re using node, but only with https://github.com/Shopify/shopify-node-api
koa isn’t used, not even by dependencies.
Still getting the error notification in Partner dashboard though.
Hi Joey,
our app is built with the shopify_python_api with server side authentication and App Bridge v 2.0.3 in front view. We are also getting this message. Any suggestions?
@HeartCoding , does the banner include information about which specific EASDK calls were made? Also, when did the banner first appear?
I am asking because I looked through the shopify_python_api codebase and I don’t notice anything that would cause EASDK calls to be made.
Thanks @JoeyF for your response.
The warning has indeed changed today. It now provides information about the remoteRedirect method which we use to make sure our app loads in an iframe inside Shopify.
We could track down the issue to the following code:
and have replaced it with this code:
Thanks to this commit.
We will deploy the fix tomorrow and hopefully it will solve the issue.
I guess we will know in 10 days.
I hope the code snippet will help anyone else with the same problem.
Thanks and cheers,
Norbert
@HeartCoding , thank you so much for posting the detailed update!
Glad you managed to find the root cause (and fix it).