BUG - Script tag deprecation on Liquid storefronts Email is Wrong

Extensions
1

I just received an emailed from Shopify stating this:

We are completing the script tag deprecation with a change to Liquid storefronts that will affect your merchants using 2 of your apps: xxx, xxx

I haven’t used script tags in YEARS. All my apps run on app embeds. I have a feeling that some ancient merchants may be caught in some limbo in your system which is causing my apps to be flagged.

The email continues to state:

October 1, 2026: You can no longer create or update script tags. Existing script tags will keep running but merchants who install affected apps from this date see a banner warning that parts of the app will stop working on March 1.

PLEASE DO NOT ADD A WARNING BANNER - EVERYONE WILL MESSAGE US! THIS IS CRAZY.

The email should explain how the heck we prove to you that we dont use script tags. Once of my apps literally has 15 app embeds! I haven’t used script tags since 2024, maybe even 2023.

2

I dont even have the script tags scope setup on any of the apps. I remember rest api required the scope. I’ve never used the graphql version, does it require the scope?

Why would you show a warning banner if the app doesn’t even have the script tags scope setup?

I mean I can somewhat understand showing a script tags banner to merchants that somehow have ancient script tags setup, but to show it to everyone that is going to install an app?? That’s a big bug!

3

Exactly the same here. I even had someone from Shopify bulk-migrate my older merchants from script tags to app extensions in the past, so I’m not really sure why my app was flagged either, or which merchants are supposedly still using script tags.

It feels a bit unfair to display this kind of flag so quickly. Would it be possible to give developers a little more time to address the issue?

I wasn’t even aware that some of my older merchants still had calls to ScriptTags that are no longer used by my app, so I didn’t have a chance to identify and clean them up before the flag appeared.

4

We no longer have the app scopes in our app, but we received this email too.

The banner should not be shown for apps that do not have this scope anymore and have published app embeds instead.

5

These warning banners have been an issue since day one. Telling (scaring) users about an app not being supported when it is 100% working is helping no one. It should not be shown to merchants at all. It’s a lie. The app is supported and even after the deadline passes it’s still supported until you guys “flip the switch”. All it does is cause confusion. Since day one we have received panic emails asking if the app is supported when it 100% was.

6

Echo everyone here. We don’t even have the scopes anymore, yet we still got the email…

7

(post deleted by author)

8

Thanks for the feedback y’all, I’ll make sure the team sees it.

The banner will only appear if an app has active script tags AND doesn’t ship either an app embed or a web pixel. Details are here.

I did spot check for a few folks here that have their partner ids/apps listed in the profile, and there doesn’t seem to be a bug:

  • Every partner has at least one app with active script tags; you can verify using the scriptTags query
    • It is possible that your apps moved away from creating new script tags, but there might be older stores still using them
  • Most of the apps ship either app embeds or web pixels, meaning that the notice banner won’t show up for new installs
9

Thanks for the clarification Misha. Those warnings banners can be a massive burden.

Fwiw, I ran a script tags “bulk delete” script long ago, but I suspect merchants whose accounts are frozen / paused were unreacheable since their api key would have also be frozen. This is probably one reason there are still lingering script tags out there.

The bug wasn’t related to there being some lingering script tags out there - it was that the email explained that the banner would be appearing indiscriminately within 5 days.

10

Thanks @misha. If we bulk-delete the remaining legacy script tags by processing each installed store through a queue, how can we confirm that Shopify no longer considers our app affected and that no warning banner will appear during installation?

As others have mentioned, I’m concerned that frozen stores may be inaccessible through the API but could still cause our app to be flagged. How should we handle stores where we can’t remove the remaining script tags?

Is the app’s status updated automatically after cleanup? If so, how long does that take? If the banner persists, should we contact Partner Support, or is there a specific process to request a review?

I still feel that October 1st leaves very little time to audit thousands of stores, complete the cleanup, and verify that the warning won’t affect new installs.

11

Totally fair callouts. Let me follow up with the team and get back to you asap.
Once I hear back, I’ll consolidate the topics and post a reply in [Deprecation] Script tags will stop running on March 1, 2027

12

@misha We have a different kind of issue that’s related to older stores.

We also bulk deleted script tags some time ago and rechecked everything again yesterday. But we have 107 stores that were frozen, re-oppened their stores, re-logged in to our app and updated their access scopes (as we removed script tags).

Now even if we wanted - we cannot delete script tags for those stores as we get an error from Shopify API: This action requires merchant approval for write_script_tags scope.

If Shopify could remove those from their end - would be amazing.