Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug] Solution export fails again on 9.2.26091.144 — code app package container missing (404 in GetBlobBytes) for every publish since 2026-09-24 ~08:00 UTC (regression of #464)

未关闭
#467 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
20/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
typescript, vite
领域
cloud, devops

调研方向

No repository file or test is named. Begin by reproducing the failure with pac solution export and compare a working and broken code app using the listed container and package-blob checks; use the support case and captured ActivityIds to determine whether an actionable repository change exists. Done means code app versions consistently retain their package containers and export successfully through pac, the maker portal, and the Web API.

由索引模型根据 Issue 内容生成。

描述

bug

Follow-up to #464 / #454, which were closed as fixed on 2026-09-22. We see the problem again, with a slightly different signature.

Environment
  • Region: Germany (crm16), Dataverse 9.2.26091.144 (DEV and target env)
  • Publish client: pac 1.52.1 (pac code push), @microsoft/power-apps ^1.2.5, Vite 7
Symptom

pac solution export / maker portal / Web API export (managed and unmanaged) fails with "An unexpected error occurred". Async operation message:

HttpRequestException: 404 (The specified resource does not exist.)
  at StorageBlobDataProvider.GetBlobBytes
  at CanvasAppHandlerInternal.MarkBlobForExportAndUpdateXmlNode
  at CanvasAppHandlerInternal.AddBlobFileXmlNodes
  at CanvasAppHandler.ExportItem

(#464 had 401 NoAuthenticationInformation in ListBlobNamesAndUrisInContainer — the listing seems fixed, but the package blob itself is not there.)

Observations

Using the same check as in #464 (anonymous ?restype=container&comp=list on properties.appUris.codeAppPackageUri), plus container properties and a direct index.html GET:

App (same env) Last publish (UTC) Container Solution export
App A 2026-09-24 05:22 exists (200) ✅ works
App B 2026-09-24 08:26 … 2026-09-25 06:16 (18 publishes) 404 – resource does not exist ❌ fails
App C 2026-09-21 12:19 404 (not tested)
  • App B's version history: all 28 versions up to 2026-09-09 have a readable container, all 18 versions since 2026-09-24 08:26 UTC have none. 5 consecutive republishes on 2026-09-25 06:15–06:16 UTC: all 404.
  • App A had two broken versions on 2026-09-21 and good ones again from 2026-09-23 — so it is intermittent/server-side, not app-specific.
  • A solution import into the target env on 2026-09-24 05:24 UTC also produced a version without container.
  • Same storage account and container naming pattern for good and bad versions; no difference in app metadata (almMode, status, client versions).
  • The apps themselves still run in the player; only the export path is broken.
Impact

All ALM routes for code apps are blocked again (export, pipelines, solution checker). The only practical advice until a fix: don't republish a code app that still exports.

A Microsoft support case has been opened; ActivityIds / async operation IDs / timestamps can be shared privately.

主要语言
TypeScript
星标
504
派生
145
平均合并
4 小时 3 分钟
30 天内合并 PR
1

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/PowerAppsCodeApps 的其他 Issue

查看 microsoft/PowerAppsCodeApps 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。