Store not found

Topic summary

A developer is encountering authentication issues when trying to access a specific page in their Shopify app built with the Remix template.

Key symptoms:

  • Login error appears when attempting to open the page
  • Sometimes redirects to the last opened page
  • Error message: “accounts.shopify.com refused to connect”
  • Console logs show shop: null during authentication attempts

Context:

  • The same functionality works correctly in their demo app
  • Issue only occurs in their production/final app
  • Problem appears to be related to the shop parameter not being passed or recognized during the authentication process

The discussion remains open with no resolution yet provided.

Summarized with AI on October 27. AI used: claude-sonnet-4-5-20250929.

when i try to open this page, it showing this login error and some time redirect to last open page, after login it shows this error accounts.shopify.com refused to connect.

11:53:10 │ remix │ [shopify-app/INFO] Authenticating admin request | {shop: null}

and in console it showing shop as null so what could be the problem here i got stucked here

but in my other demo app this page is working fine but in my final app its not working

i’m using remix template to develop app.

Seeing accounts.shopify.com refused to connect usually means the embedded app can’t be rendered in the admin because the OAuth process hasn’t completed or the domain is not authorized. Here are some things to check:

  • Make sure you are passing the shop parameter when navigating to your app. In embedded apps built with the Remix template the /?shop=your-store.myshopify.com query string is used to bootstrap the OAuth flow. If shop is null in your logs it means the parameter is missing.

  • Check your .env configuration – SHOPIFY_APP_URL (or APP_URL) must match the HTTPS URL where the app is running (for local development this is usually an ngrok tunnel). If the URL stored in the app settings on your Partner dashboard does not match, Shopify will refuse to frame it.

  • Confirm that third party cookies are enabled in your browser. The Admin relies on cookies to authenticate embedded apps; if they are blocked, the iframe will show a “refused to connect” message. You can also test using Chrome Incognito with third‟party cookies allowed.

  • Upgrade your Shopify remix template and dependencies (@shopify/shopify-app-remix, @shopify/app-bridge) to the latest versions. There was a recent change to the Shopify Admin domain (accounts.shopify.com) and older versions of App Bridge needed patching.

  • In your Remix loader logic, ensure you redirect to /auth when the session is missing rather than rendering the app. The Shopify example templates show how to validate the shop session and re‑initiate OAuth.

  • Finally, double‑check that the app is installed on the store you’re testing against. If you created a second store, you need to install the app there via the Partners dashboard.

Applying these steps should resolve the “shop null” issue and let your embedded app load correctly.

There is an alternative way: You can always ask for help from this app team when encountering the issue inside them.

It sounds like your app is having trouble detecting the shop parameter during authentication.
That’s why you’re seeing this line in the logs:

[shopify-app/INFO] Authenticating admin request | {shop: null}

and the accounts.shopify.com refused to connect error.

Here are a few things you should check:

  1. Missing shop parameter
    Make sure the app always receives the shop query parameter when loading.
    Example:

    https://your-app-domain.com/auth?shop=teststore.myshopify.com
    
    

    If shop is missing, Shopify can’t authenticate the request and shop becomes null.

  2. App bridge and session handling
    In Remix apps, ensure you have the correct <ShopifyAppBridgeProvider> setup and that the app is loading inside the Shopify admin (embedded).
    If the app tries to open outside the embedded context, it may trigger a redirect loop or the “refused to connect” iframe error.

  3. Environment variables
    Double-check that your .env file has the correct values for:

    SHOPIFY_API_KEY=
    SHOPIFY_API_SECRET=
    SCOPES=
    SHOPIFY_APP_URL=
    
    

    Even a small typo or missing URL scheme (https://) can break authentication.

  4. Auth callback route
    Make sure your callback route (/auth/callback) matches exactly in both:

    • Shopify Partners dashboard (App setup)

    • Your Remix app route structure.

  5. Compare with your working demo app
    Since your demo app works, compare these files:

    • shopify.server.ts

    • .env values

    • server.js or index.js where you handle shopifyApp({ ... })
      A missing or incorrect config there usually causes shop: null.


:white_check_mark: In short:
The problem happens because Shopify can’t identify the store (shop = null).
Fix the redirect URL or ensure the app always starts with the ?shop=store.myshopify.com parameter, and confirm your .env + callback URLs match.