Skip to content

[AspireE2E] Failed to create Aspire Python Starter App and Express TypeScript App after installing Aspire 13.4.0 #17584

Closed

Description

@jinzhao1127

REGRESSION INFO: Works well on Aspire 13.3

INSTALL STEPS

  1. Clean machine: Windows11 25h2 x64
  2. Install 10.0.301 SDK
  3. Install Aspire CLI 13.4 : iex "& { $(irm https://aspire.dev/install.ps1) } -Quality staging"
  4. Add feeds

REPRO STEPS

  1. Open CMD, run following command to create a Aspire Python Starter App
     aspire new aspire-py-starter --name AspirePythonApp
    

ACTUAL
The project always keep creating status, can't be complete
Image
After a log time:
Image

CLI log: ‪\\vwdbuild01\temp\v-zhajin\Bug\#17584\cli_20260528T054216_2f9363b1.log

Note:

  1. This issue also reproduces on Express/React, TypeScript AppHost
  2. This issue does not reproduce on Aspire ASP.NET Core/Blazor andASP.NET Core/React, C# AppHostproject
  3. Open the project folder, It has contains some contents, but it failed to run with error Timed out waiting 120s for AppHost to start. If the AppHost is still building or starting
Image

Activity

  1. joperezr commented on May 28, 2026

    @joperezr
    Member
    🤖 Aspire triage pass — 2026-05-28 06:48 UTC

    Area: area-polyglot, area-templates, area-cli
    Kind: regression
    Repro: yes-minimal — see install/repro steps in issue body (sections INSTALL STEPS and REPRO STEPS)
    Affected version(s): Aspire CLI 13.4.0 (staging); works on 13.3
    Severity: S2 — aspire new hangs indefinitely creating Python Starter and Express/React TypeScript AppHost templates; no workaround for those template flavors (ASP.NET Core/Blazor and ASP.NET Core/React C# AppHost still work).

    Urgency: 🔴 release-blocking — recommend milestone 13.4
    Reason: Explicit regression vs. 13.3 in a core aspire new scenario for polyglot templates (Python, Express/TypeScript), with no workaround. Polyglot template work landed heavily in 13.4 (e.g. recent area-polyglot PRs #17510, #17508, #17434), making this a likely 13.4-introduced regression. Given the release snap, this needs a human ship-call.

    Suggested owner(s): Mitch Denny (@mitchdenny) (active in area-cli + area-templates + area-polyglot in the last week), backup Sébastien Ros (@sebastienros) (most recent area-polyglot work)
    Evidence:

    Confidence: medium — 13.3-vs-13.4 regression is reporter-stated; the exact regressing PR was not bisected.
    Needs human?: yes — 13.4 recommendation requires human confirmation (release-blocking, snapped release)

    Dry-run mode — no labels or milestone applied. Reply /triage apply to promote, or edit and reapply.

  2. added this to the 13.4 milestone on May 28, 2026
  3. sebastienros commented on May 28, 2026

    @sebastienros
    Contributor

    This seems to be the issue fixed by #17573
    Waiting for the new build to be available to retry.

  4. sebastienros commented on May 29, 2026

    @sebastienros
    Contributor

    Verified fixed in 13.4.0+d8c4e9645a029b4fca8ce20eb00def5526806eda

  5. EmilyFeng97 commented on Jun 1, 2026

    @EmilyFeng97

    Verify this bug on the latest aspire CLI 13.4.0+e13850995727767ba26088932630342417745f40, it was fixed.

    Image
  6. locked and limited conversation to collaborators on Jul 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions