themeFilesDelete results in internal error

GraphQL Admin API Troubleshooting
1

Hi,

I have a public application that makes use of the write_themes access scope and has exemption for the Assets API in order to modify theme files.

Now that I’m migrating everything to GraphQL, I’m using themeFilesUpsert and themeFilesDelete mutations to delete/create/update theme assets.

Based on the docs, both mutations need the same access scopes. However, while themeFilesUpsert mutation runs successfully and returns the expected response, themeFilesDelete mutation returns an error, namely “Internal error”. After I executed the delete mutation, I checked my theme files in the Shopify theme editor and I saw the file got deleted though…

I’ve executed the steps above multiple times with the same results.

Here’s the details of the last execution for the themeFilesDelete mutation:
Time: 4:18 PM CET

{
  "errors": [
    {
      "message": "Internal error. Looks like something went wrong on our end.\nRequest ID: 514edb9d-9c00-40e6-8db4-d7458876f9be-1731511115 (include this in support requests).",
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "requestId": "514edb9d-9c00-40e6-8db4-d7458876f9be-1731511115"
      }
    }
  ],
  "data": null
}

I would really appreciate any input on this.

1 Like
2

Hi ggurkal,

Are you still experiencing this issue?

3

Hi @Liam-Shopify,

Yes, still experiencing the same issue.

The funny thing is, everything works well when i use Shopify’s GraphiQL App, but not when I use curl.

4

Hi again - I’ve gotten in touch with our product team and there is a bug with the delete mutation we’re working on which could be related to this. Will update here when we’ve released a fix.