When you installed on your own development store, did you use the link provided by the partner dashboard (more actions > test on development store > install app) or did you manually create a permission URL? For the production store, are you using the custom install link created by Shopify?
Do you have logic written into your app so that when the store hits it, you detect whether or not they already have it installed and, if not, you route them to the OAuth permission URL?
I used test on the development store but I created a permission URL to update token.
For the production store I have used the custom install link created by Shopify .
Going to the install link I am redirected to the custom url and I got the url with the hmac, shop and timestamp. State and code are missing and I cannot proceed with the token request. Should I extract them from the hmac or something else? The prompt is not shown.
When I use a created authorization link with the api I get the prompr but the install button is not enabled.
Hmm that’s weird. When you say custom URL, do you mean the OAuth your callback URL or your app’s URL as if it’s already installed? Can you paste in the URL?
When you say state and code are missing and you can’t exchange for a token, in this case that shouldn’t be possible regardless because since they never authorize the app, the app never shows as “installed” when that shop looks at their Apps, correct?
I’m also not sure why the install button is greyed out, maybe Shopify changed it so you can’t just send a merchant a regular OAuth permission URL (even if it’s a custom app for their shop). Is there any kind of error message that you see on that page?
Bump. Same issue. All I needed was a proxy URL. So, I created a partner app, added the proxy URL information, and kept the default app domain of “example.com”. I then created a merchant link to install it into our product store. When I open that link, I am just immediately redirected to “https://example.com”, and it has query arguments like “hmac” and “host” in the URL. The documentation seems to imply, in many places, that all I need to do is create that link and access it, and my store will magically have access to that app. Therefore, the documentation is completely useless in general since these basic steps seem incorrect/incomplete.