write_themes_assets access needed but it does not exist

[TonyKhaov]

Hello I already have the read_themes and write_themes access but when running this mutation (themeFilesUpsert) with the latest API (2024-10) : https://shopify.dev/docs/api/admin-graphql/2024-10/mutations/themeFilesUpsert

`#graphql
      mutation themeFilesUpsert($files: [OnlineStoreThemeFilesUpsertFileInput!]!, $themeId: ID!) {
        themeFilesUpsert(files: $files, themeId: $themeId) {
          job {
            done
          }
          upsertedThemeFiles {
            filename
          }
          userErrors {
            field
            message
          }
        }
      }
`

I get this error message:

Access denied for themeFilesUpsert field. Required access: The user must have write_themes and write_themes_assets.

But the problem is write_themes_assets seems to not exist I have checked online and Shopify never mentions it…

And I’m having this error when trying to run app deploy script:

[2Thomas]

I encountered the same issue and hope Shopify can provide a solution.

[tahacakir]

Also facing the same problem. Rest api is deprecated and i am forced to use this mutation but unfortunately can not.

[alexz]

I have the same issue. write_themes_assets should be a sub-scope of write_themes. This is going to create a terrible user experience for existing apps forced to migrate from the REST Admin API to the GraphQL Admin API, as storeowners are going to have to re-permission the app because we’ll need to request new scopes. It’s also frustrating that the scopes haven’t been rolled out properly:

These scopes are invalid - [write_themes_assets]

Please can we see more of a joined-up approach within Shopify, so where different teams are responsible for different aspects of a mandated policy, they work together to ensure that developers aren’t left stuck in the middle?

[rachelplatt625]

Same issue here! Hoping for a solution soon.

[pranav1]

Same issue.

[dot_amir]

Same issue here.
I have come to believe that Shopify hates its developers. Constantly changing the API and its tools, deprecating a tool suddenly, and now THIS!

It takes a lot of patience to develop an app for Shopify.

[shakibul_islam]

I’m encountering the same issue and am stuck in my development process.

[gabrysabatino]

Same issue, I started few days ago to develop my first app and encountered in this mistake

[PeterFaster]

Same here, what was that?

[dot_amir]

For anyone who faced this issue, I found out that since 2024/04 Apps with public distribution should apply for specific access scopes from this form:
https://docs.google.com/forms/d/e/1FAIpQLSfZTB1vxFC5d1-GPdqYunWRGUoDcOheHQzfK2RoEFEHrknt5g/viewform

I hope this helps you.

[PeterFaster]

I submitted it, and it was approved. Later, I deleted the app and created a new one, but I don’t think that’s the issue

[dot_amir]

Well, they approved the access scopes for the app you have applied for. When you create a new one it shouldn’t have the access scopes because you mention your app name in the form.

So I guess you should apply for your new app as well.

[bensenescu]

There are some other threads about this on the dev forum: https://community.shopify.dev/t/add-liquid-file-to-the-live-shopify-theme/719

Apparently, there is this form that you can fill out to request access, but it doesn’t seem like anyone’s really had this solve their problem so far: https://community.shopify.dev/t/issue-with-write-themes-and-write-themes-assets-scopes-in-graphql-api/633/5

[naughtyduk]

I have this working and I’ve documented the solution here:

https://www.linkedin.com/pulse/so-you-want-use-writethemesassets-shopify-graphql-api-naughtyduk-8jkfe/