You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are developing an app where each merchant might use a different set of webhooks, depending on which features of the app they use.
When shopifyApp.auth.path (/api/auth) is called, the app registers webhooks that are defined in the app and deletes all other webhooks. But as the number of webhooks to be registered differs from merchant to merchant, we cannot statically define a set of webhooks for all merchants that use the app.
For this reason it would be great if we could disable the webhook handling in shopify-app-js, so we can implement a custom webhook handling instead. Currently all of our registered webhooks will be removed when shopifyApp.auth.path (/api/auth) is called which happens e.g. when the merchant gets a new browser session (the merchant closes their browser and opens a new browser and access the app again).
I tried with the following, but it seems to be overridden:
The following does not work either:
The issue seems to be (at least, not limited to) that registerWebhooks is called on authCallback:
Kind regards,
-Louise
The text was updated successfully, but these errors were encountered:
Overview
We are developing an app where each merchant might use a different set of webhooks, depending on which features of the app they use.
When shopifyApp.auth.path (/api/auth) is called, the app registers webhooks that are defined in the app and deletes all other webhooks. But as the number of webhooks to be registered differs from merchant to merchant, we cannot statically define a set of webhooks for all merchants that use the app.
For this reason it would be great if we could disable the webhook handling in shopify-app-js, so we can implement a custom webhook handling instead. Currently all of our registered webhooks will be removed when shopifyApp.auth.path (/api/auth) is called which happens e.g. when the merchant gets a new browser session (the merchant closes their browser and opens a new browser and access the app again).
I tried with the following, but it seems to be overridden:
The following does not work either:
The issue seems to be (at least, not limited to) that registerWebhooks is called on authCallback:
Kind regards,
-Louise
The text was updated successfully, but these errors were encountered: