Script Tags are not being registered

[jagthedrummer]

Issue summary

Before opening this issue, I have:

• Upgraded to the latest version of the package
  • shopify_app version: 22.3.2
  • Ruby version: 3.3.2
  • Operating system: MacOS / Linux
• Set log_level: :debug in my configuration, if applicable
• Found a reliable way to reproduce the problem that indicates it's a problem with the package
• Looked for similar issues in this repository
• Checked that this isn't an issue with a Shopify API
  • If it is, please create a post in the Shopify community forums or report it to Shopify Partner Support

When a shop installs the app the scripttags specified in the initializer aren't registered.

Expected behavior

The scripttags listed in the initializer should be registered.

Actual behavior

They are not registered.

Steps to reproduce the problem

1. Install an app with scripttags in a new shop.
2. See that the script tag is not registered.

It looks like maybe something on the Shopify side broke this starting sometime in mid June.

I realize that script tags are deprecated, but all of the info I can find says that they should continue to work until August of 2025.

[matteodepalo]

Hi @jagthedrummer thank you for opening this we can take a look.

[lizkenyon]

Hey there @jagthedrummer!

The script tag manager was removed in version 22. In the upgrading guide you can find our recommendation.

I do see that we still have the scripttags configuration in the shopifyApp object, so I can understand where the confusion is coming from. The team will look into clarifying this.

[jagthedrummer]

@lizkenyon, I see.

FWIW, as a developer working in the Shopify ecosystem I feel it's pretty unfriendly (bordering on hostile) to purposefully remove working code over a full calendar year before the functionality supported by that code is slated to be dropped.

[lizkenyon]

I think that is very valid feedback. I will share with the team.

[jagthedrummer]

@lizkenyon Any word on this? It would be great to have the ScriptManager added back since that feature isn't actually deprecated yet.