Compliance webhooks error.

Plz help me one. I'm using gadget and connected to shopify. when I try to publish the shopify app, I encountered this error. FYI: I already updatd the shopify.app.toml file in gadget. [webhooks] api_version = "2025-07" [[webhooks.subscriptions]] compliance_topics = ["shop/redact"] uri = "https://origami.gadget.app/api/webhooks/shopify" but I have still same issue. I would appreciate if someone could help me. šŸ™
No description
38 Replies
Chocci_Milk
Chocci_Milk•2w ago
Please note that you need to assign all 3 compliance topics there and deploy the changes to Shopify. We don't deploy the toml configurations or Shopify extensions for you You can alternatively set the compliance webhook URL in the Partner dashboard
luc@s
luc@sOP•2w ago
Thanks for your info I can't see the configuration tab in my partner dashboard. what is the reason? [webhooks] api_version = "2025-07" [[webhooks.subscriptions]] compliance_topics = ["customers/data_request", "customers/redact", "shop/redact"] uri = "https://origami--development.gadget.app/api/webhooks/shopify" this is my toml file We don't deploy the toml configurations or Shopify extensions for you what does mean this? this means even if I update the toml file like this, can't resolve current issue?
Chocci_Milk
Chocci_Milk•2w ago
2 things: - you should not be submitting your development application for public app review. Connect your production environment to a new Shopify application and start the review on that Shopify app - I believe that you don't see the configuration page because of the new Dev Dashboard rollout from Shopify. You would need to talk to them to confirm this
luc@s
luc@sOP•2w ago
this is production environment.
No description
Chocci_Milk
Chocci_Milk•2w ago
The toml configs that you shared with me are for the dev environment based on the URL: https://origami--development.gadget.app/api/webhooks/shopify
luc@s
luc@sOP•2w ago
oh sorry, actually, this is my toml file. [webhooks] [webhooks] api_version = "2025-07" [[webhooks.subscriptions]] compliance_topics = ["customers/data_request", "customers/redact", "shop/redact"] uri = "https://origami.gadget.app/api/webhooks/shopify" I updated correctly I tried the production gadget app and updated toml file correctly. but I had same issue. [webhooks] api_version = "2025-07" [[webhooks.subscriptions]] compliance_topics = ["customers/data_request", "customers/redact", "shop/redact"] uri = "https://origami.gadget.app/api/webhooks/shopify"
Chocci_Milk
Chocci_Milk•2w ago
Ok, so what I would recommend you do now is to run the command yarn shopify:deploy:production. That will deploy your production configs to Shopify
luc@s
luc@sOP•2w ago
where can I run this cmd? I'm using deploy button in gadget platform>
No description
luc@s
luc@sOP•2w ago
one question. I can see this deploy button in development environment only? when I click this button, deployed the development to production? am I right? šŸ™
No description
Chocci_Milk
Chocci_Milk•2w ago
The deployment button in Gadget is for the code that we host. We don't run the Shopify CLI commands for deploying tomls and extensions for you. Please take a look at the Shopify CLI docs written by Shopify for more information. The command I'm talking to you about will most likely need to be run on your local terminal as deployments often create files and the Gadget terminal doesn't yet allow that
luc@s
luc@sOP•2w ago
Okay, Thanks so much. let me try now
Chocci_Milk
Chocci_Milk•2w ago
No problem. Let us know if you run into more issues
luc@s
luc@sOP•2w ago
I'm try to use shopify cli
No description
luc@s
luc@sOP•2w ago
I checked the configured toml file but it has only [webhooks] api_version = "2025-07" not contains the [[webhooks.subscriptions]]
Chocci_Milk
Chocci_Milk•2w ago
You need to make sure that you have your application code on your local machine, then run the command from the application's folder. Please take a look at these docs: https://docs.gadget.dev/reference/ggt#ggt-reference
luc@s
luc@sOP•2w ago
how can I update it? I just installed ggt and then what should I do?
Chocci_Milk
Chocci_Milk•2w ago
Change directory to the application folder and run the yarn command I shared with you
luc@s
luc@sOP•2w ago
oh, sorry but. what is the application folder?
Chocci_Milk
Chocci_Milk•2w ago
The local folder that has your Gadget application code in it
luc@s
luc@sOP•2w ago
I only worked on online gadget platform editor so far. I'm not familar with Gadget yet
luc@s
luc@sOP•2w ago
can't I use this terminal?
No description
Chocci_Milk
Chocci_Milk•2w ago
The command I'm talking to you about will most likely need to be run on your local terminal as deployments often create files and the Gadget terminal doesn't yet allow that
What I meant there was that Shopify CLI deployment command runs create files and our terminal doesn't currently allow that
luc@s
luc@sOP•2w ago
Thank you so much bro šŸ™ resolved that issue.
luc@s
luc@sOP•2w ago
btw, why I can't click the submit for review button yet?
No description
Chocci_Milk
Chocci_Milk•2w ago
No problem! Let us know if you have anymore questions
luc@s
luc@sOP•2w ago
need to handle Embedded app checks?
Chocci_Milk
Chocci_Milk•2w ago
The last checks need to pass for you to submit
luc@s
luc@sOP•2w ago
OMG
Chocci_Milk
Chocci_Milk•2w ago
They run at random times You also need to create your listing if you haven't already
luc@s
luc@sOP•2w ago
one question. šŸ™ I configured the gadget in my next.js project. I used this cmd. npm install @gadget-client/origami but it is auto connected to the development. how can I connected to the production.
No description
luc@s
luc@sOP•2w ago
No description
luc@s
luc@sOP•2w ago
so I have this error when I use the production api key: Error: [Error [CombinedError]: [GraphQL] GGT_INVALID_API_KEY: Invalid API key. Please ensure you're passing an API Key directly copied from the Gadget Editor, which is a string starting with gsk-.] {
luc@s
luc@sOP•2w ago
No description
Chocci_Milk
Chocci_Milk•2w ago
I think that's cause you're using the development client. You should update the package using: yarn add @gadget/client@latest-production and use that one in production. Btw, could you please start new threads for new issues?
luc@s
luc@sOP•2w ago
OK. Done. Sir šŸ™
Chocci_Milk
Chocci_Milk•2w ago
Thanks, its just to keep issues separate and make them easier for other users to read I'm going to mark this as closed since this has been resolved
Gizmo
Gizmo•2w ago
Do you like this answer? ​
luc@s
luc@sOP•2w ago
yup sure

Did you find this page helpful?