Custom distribution install link returning "OAuth error: application cannot be found" error

We have created a custom app via the Dev Dashboard and configured it with custom distribution. However, when the store owner clicks the install link, they receive the following error:

“OAuth error: application cannot be found” Oauth error application_cannot_be_found: Could not find Shopify API application with api_key <>

This issue is not isolated to a single store — we have encountered the same error across multiple stores.

What we verified:

  • The app exists in the Dev Dashboard and is active
  • The Client ID in the install link matches the app’s actual Client ID
  • Custom distribution is properly configured with the target store assigned
  • The install link was generated directly from the Dev Dashboard distribution page
  • The store owner is logged into the correct store when clicking the link
  • The error occurs immediately on clicking the link — no consent screen is shown
  • We also tested installing on a store outside the Plus organization and received a different error (invalid_link_organization), confirming the link validation is partially
    working but failing on app lookup

Questions:

  1. Why is Shopify unable to find the app when the Client ID is valid and the app is active in the Dev Dashboard?
  2. Is there a known issue with custom distribution install links for apps created via the Dev Dashboard?
  3. Are there any additional steps required after app creation for the install link to become functional?

Hi @Shreyansh_Gupta,

It sounds like you’ve checked everything pretty thoroughly, and I’m not quite sure what would be causing the error in this case without looking at any specific examples.

If you can provide us with the x-request-id displayed on the error page if any, I can help take look further.

Alternatively, I would recommend reaching out to our Shopify Support Team via the Shopify Help Center, while logged into your Partner Account, and we can help take a more detailed look into the issue in a fully authenticated support interaction.

If you do reach out via the Help Center, it would also be very helpful if you have a HAR file recorded, showing the error occurring, so we can see the exact events in the browser at the time of the error. Here’s some information on how to record a HAR file from the most popular web browsers.


Note: HAR files can contain login information/credentials and session cookies. For data privacy purposes, please avoid entering/recording personal details such as passwords and credit card information. It would be best to record the HAR via an Incognito window.

Chrome

  1. Open the Developer Tools from the menu (Menu > More Tools > Developer tools), or by pressing Ctrl+Shift+C on your keyboard.
  2. Click on the Network tab.
  3. Look for a round button at the top-left of the Network tab. Make sure it is red. If it is grey, click it once to start recording.
  4. Check the box next to Preserve log.
  5. Use the clear button (a circle with a diagonal line through it) right before trying to reproduce the issue to remove any unnecessary information.
  6. Reproduce the issue (E.g. load/refresh the page that has errors, or perform the action that has errors).
  7. Save the capture by right-clicking on the grid and choosing Save as HAR with Content. Alternatively, you can click the export/save button (downward arrow with a line underneath).

Safari

  1. In Safari, go to the page where the HTTP(s) URL Sequence needs to be monitored.
  2. Enable Developers Tool by going to Safari > Preferences > Advance > Click Show Develop menu in menu bar
  3. In the menu bar at the top, click Develop and select Show Web Inspector.
  4. Click the Resources tab and enable Preserve Logs.
  5. Go to the Network tab.
  6. Reproduce the issue (E.g. load/refresh the page that has errors, or perform the action that has errors).
  7. After successfully performing the activity, lick the Export icon and save the HAR file.

Firefox

  1. In Firefox, go to the page where the issue is occurring.
  2. Click the Firefox menu available at the top-right of your browser window and select Web Developer → Network, or simply press the F12 button. The Developer Tools window opens as a docked panel at the side or bottom of Firefox.
  3. Click the Network tab.
  4. Click on Network Settings and enable Persist Logs.
  5. Now refresh the page and perform the activity that needs to be recorded i.e. the activity that produces the error.
  6. After successfully performing the activity, right-click on any row of the activity pane and select Save all as HAR or click the Export HAR icon and select Save all as HAR to download the HAR file.

Edge

  1. Open Microsoft Edge and navigate to the page where the issue is occurring. Note: This is tab and window dependent, so if the issue occurs in a new tab or window, the HAR recording needs to be done in that new tab or window.
  2. Click the horizontal ellipsis menu button and select More Tools, then click Developer Tools.
  3. Click the Network tab, and then click the Record button in the upper left corner of the tab and verify that it is red, if it is grey, click it to start recording.
  4. Check the box Preserve Log.
  5. Click the Clear button to clear out any existing logs from the Network tab. Note: Do not close the Developer Tools panel. This will end recording and the HAR file will be lost.
  6. Reproduce the issue while the network requests are being recorded.
  7. Once you have reproduced the issue fully, right-click anywhere on the grid of network requests and choose Save as HAR with Content, and save the file to the computer.

Hi @Shreyansh_Gupta

Can you see the `client_id` parameter in your URL?

Hey @Shreyansh_Gupta,

I just wanted to follow up here and see if you still needed help with this, or if you were able to reach out through the Help Center and get this resolved?

If you no longer need help, please let us know and we can mark this thread as solved.