We’re trying to deploy to the new dev stores with our internal CD process.
I opened a ticket on github and was referred here to ask the question.
opened 06:01PM - 03 Jul 25 UTC
closed 11:25AM - 10 Jul 25 UTC
Type: Bug
### Please confirm that you have:
- [x] Searched [existing issues](.) to see if… your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
- [x] Reproduced the issue in [the latest CLI version](https://www.npmjs.com/package/@shopify/cli).
### In which of these areas are you experiencing a problem?
App
### Expected behavior
When running shopify app deploy during CI, and given the proper configuration, I would expect the app to deploy without interactive prompts to the next gen dev store.
### Actual behavior
Interactive environment not supported when running in CI mode, or
'To run this command, log in to Shopify.
13:58:03 User verification code: MSTB-QDBL
13:58:03 👉 Open this link to start the auth process:'
### Verbose output
<details>
<summary>Verbose output</summary>
These variables yield the following result:
CI=true
SHOPIFY_CLI_THEME_TOKEN=<token generated from theme access app>
SHOPIFY_FLAG_FORCE=1
SHOPIFY_FLAG_STORE=ourstore-alpha.myshopify.com
```
To run this command, log in to Shopify.
12:55:15 ╭─ error ──────────────────────────────────────────────────────────────────────╮
12:55:15 │ │
12:55:15 │ Authorization is required to continue, but the current environment does │
12:55:15 │ not support interactive prompts. │
12:55:15 │ │
12:55:15 │ To resolve this, specify credentials in your environment, or run the │
12:55:15 │ command in an interactive environment such as your local terminal.
```
These variables also yield the same result as above
CI=true
SHOPIFY_API_KEY=<client id from the dev dashboard for the app we're trying to deploy>
SHOPIFY_API_SECRET<secret from the dev dashboard for the app we're trying to deploy>
SHOPIFY_FLAG_FORCE=1
SHOPIFY_FLAG_STORE=ourstore-alpha.myshopify.com
If I set CI to false, we get
CI=false
SHOPIFY_API_KEY=<client id from the dev dashboard for the app we're trying to deploy>
SHOPIFY_API_SECRET<secret from the dev dashboard for the app we're trying to deploy>
SHOPIFY_FLAG_FORCE=1
SHOPIFY_FLAG_STORE=ourstore-alpha.myshopify.com
```
To run this command, log in to Shopify.
13:54:29 To run this command, log in to Shopify.
13:54:29 User verification code: ZPHF-GXCD
```
</details>
### Reproduction steps
We're trying to deploy an app to our next gen dev store using several variations of the following configuration.
CLI=true
SHOPIFY_CLI_THEME_TOKEN=<token generated from theme access app>
SHOPIFY_FLAG_FORCE=1
SHOPIFY_FLAG_STORE=ourstore-alpha.myshopify.com
And running this command in our CI:
npm install -g @shopify/cli@latest
shopify app deploy --path apps/shopify/dist
We've also tried using variations of the following environment variables:
SHOPIFY_CLI_PARTNERS_TOKEN (but this isn't using partners, its using next gen dev stores)
SHOPIFY_API_KEY=<client id from the dev dashboard for the app we're trying to deploy>
SHOPIFY_API_SECRET<secret from the dev dashboard for the app we're trying to deploy>
Each of these yield some version of 'login to authenticate', or this environment doesn't support interactive mode.
### Operating System
Ubuntu-24.04
### Shopify CLI version (`shopify --version`)
using @shopify/cli@latest
### Shell
_No response_
### Node version (run `node -v` if you're not sure)
_No response_
### What language and version are you using in your application?
_No response_
The recommendation was to use the partner CLI token.
However, we created the dev stores on the new dev platform, we created them on our merchant account (where our production store lives).
The partner organization has a different organization id, which yields " “You are not a member of the requested organization”.
I assume this because the merchant organization <> the partner organization. Were we supposed to create the new dev stores on the partner account?
Hey @Anthony_Weatherly !
This limitation is something our team is aware of!
Hi Josh,
Great to hear you’re finding the new developer platform helpful - we’ll be making improvements before the general release, and I’ve raised this to the team.
Hi team,
Just checking in on this thread — are there any updates on CI/CD support for next-gen dev stores?
We’re in a similar situation and would love to automate our deployments. Understanding the timeline or any planned workarounds would really help us plan accordingly.
Thanks!
Hey @Sabeeh_k , we have made some recent improvements that should help a bit. For updates, continuing to monitor the developers changelog is going to be best.