`reflex deploy --app-id X --project-name <nonexistent>` ignores the project and deploys

Open Beginner friendly

#7,296 opened on Sep 24, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 70/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: cli, python
Domain: cli, cloud

Research direction

Look at the reflex-hosting-cli package, specifically the deploy command logic. The issue is likely in the argument validation where --app-id and --project-name are handled. Start by finding the deploy command entry point, then trace how these flags are parsed and validated. Check if there's a validation step that compares the app's project with the provided project name. Running the failing command locally with debug output can help identify the missing check.

Written by the indexing model from the issue text.

Description

Package: reflex-hosting-cli (reproduced on main at ea035ea47 and on #7207 at 988718e78)

When --app-id is given, --project-name is not validated. A project name that does not exist is ignored, and a full deploy of the app starts:

$ reflex deploy --app-id <existing app id> --project-name nope-project --no-interactive
... Compiling ... Creating Production Build ... Zipping Frontend ...
[exit=0]

A new deployment appears in reflex cloud apps history <app id>. The same happens with any --project-name that doesn't match the app's actual project.

Expected: fail before building, in either of these cases:

the named project does not exist, or
--project/--project-name names a different project than the one that owns --app-id.

A mistyped or mismatched project should not trigger a deploy to whichever project the app is in.

Dominant language: Python
Stars: 28.9k
Forks: 1.8k
Avg merge: 1d 15h
Merged PRs (30d): 180

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

validate-structure inspecte challenge/work/.terraform et rend faux les labs qui ont un provider en cache Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

stephrobert/dsoxlab#238 · Opened Sep 24, 2026
Uniform probability densities use the upper bound as an interval width Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

nasa/fmdtools#40 · Opened Sep 24, 2026
_common_folder() treats a single file as the common folder; single-file archives can't be installed (4.2.8) / crash (master) Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

sublimehq/package_control#1780 · Opened Sep 24, 2026
Set 'Sample' input in 'autorun.py' to utilize 'Sample' Tab in eLog Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

pcdshub/mfx#309 · 2 comments · Opened Sep 24, 2026
niri config file addition does not respect existing optional include Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

nwg-piotr/nwg-displays#145 · Opened Sep 24, 2026

More Python issues