I’m developing a feature which will support the user to integrate their store with our application.
Our tech stack are .NET for backend and React in frontend.
The install flow is:
User login to our website
User click the button connect to store in Frontend
Here we redirect the user to the Shopify App install link and the user will login to their Shopify account and select the store they want to connect
Then Shopify redirect to the Partner App URL which is the endpoint /start in our Backend
Here we form the Oauth url with the selected shop and redirect user to the Oauth flow
After user authorize and install the app, it redirect back to the endpoint /callback in Backend
Here we exchange the code for token and complete the install process.
Hi Jordan,
My app is not embedded so I’m not using Shopify managed installs and I haven’t touched anything related to toml.
I create the public app in UI and using the authorization code grant flow.
But I think this is irrelevant because it is just the point for user to select a store. The install process is begin when browser redirect to the App URL with the shop in query string. And at this point we started the oauth immediately.
Thank you for the information.
I just wanted to check that it wasn’t something you were constructing.
The link in your first post doesn’t have a “signature” query string parameter that I would have expected so just wanted to check that and the settings as lots of people have had similar issues with managed installs being the default.
Are all the URLs you are trying to redirect to, for all the steps in the OAuth flowx in your app listed in your apps configuration for redirect urls?
Thank you. The URL actually has “signature” parameter. I just truncated it so the message won’t be too long.
All the URLs and the Oauth flow setup correctly. I have tested it with my dev store and it connect successfully.
Btw, the error detail says it got 403 http code while it should be 200 from the URL: https://xbbf0y-vp.myshopify.com/admin/oauth/redirect_to_install?…
Do you know what is the reason for this 403 error code?
Yeah I’m wondering if there’s something in your settings blocking it.
The sections I’d check, Allowed redirection URL(s) is fully correct. That your distribution method isn’t limited to install only on one store.
I’d also try it on another development store to see if it works there or if its just that one store