Critical Blocker: Shopify API Scopes & App Bridge Config Sync Failure
Hey @everyone, we're stuck in a critical configuration loop and need expert guidance.
The Problem: We have two simultaneous, conflicting errors:
Live Shopify Admin: Error: Expected app bridge to be defined in embedded context, but it was not.
Gadget Preview: Setup failed: [GraphQL] GGT_UNKNOWN: Could not fetch existing definitions from Shopify.
This points to a fundamental config mismatch between Gadget and Shopify.
Forensic Data:
App Slug: ai-copilot
Correct Client ID: [removed for privacy]
shopify.app.toml: Correctly configured with the above Client ID and our full list of 10 required scopes.
web/root.tsx: We have tried multiple versions, including the latest factory-default and several patched versions to handle App Bridge initialization. The error persists in the live environment.
The Blocker & Core Question:
We believe the root cause is a failure in the configuration handshake between Gadget and the Shopify Partner Dashboard.
During the Shopify Connection setup (legacy flow), Gadget instructs us to set these URLs in the Partner Dashboard:
App URL: https://ai-copilot--development.gadget.app/api/shopify/install-or-render
Redirection URL: https://ai-copilot--development.gadget.app/api/connections/auth/shopify/callback
However, we cannot find these input fields in the modern Shopify Partner Dashboard for our app.
Our Question: What is the modern, correct process for setting these URLs and ensuring our 10 API scopes (especially read_metaobject_definitions) are correctly synced and approved by Shopify? We suspect the UI-based scope selection in Gadget is not successfully propagating to our app's configuration in the Partner Dashboard.
Any help would be massively appreciated. Thank you!
Required Scopes:
read_products, write_products, read_product_listings, read_metaobject_definitions, write_metaobject_definitions, read_metaobjects, write_metaobjects, read_files, write_files, read_analytics
4 Replies
Hi Ishan,
We are looking into this
Are you available today for a quick call? It looks like something went awry in the set-up and I can run through it with you.
Yes I am, lets get on a call š
Ill mark this thread as closed now, if you have any further questions feel free to re-open with a reply
Do you like this answer?
ā