[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)
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 20/100
- Issue 類型
- 缺陷
- 描述清晰度
- 需要釐清
- 活躍度
- 活躍
- 技術堆疊
- typescript, vite
研究方向
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 內容生成。
描述
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:
pac1.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，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
microsoft/PowerAppsCodeApps 的其他 Issue
-
bug
難度 4/5 3-5 天 新手友好度 45/100
microsoft/PowerAppsCodeApps#465 ·
-
bug
難度 4/5 3-5 天 新手友好度 35/100
microsoft/PowerAppsCodeApps#463 · 1 則留言 ·
-
bug
難度 4/5 3-5 天 新手友好度 48/100
microsoft/PowerAppsCodeApps#462 ·
-
bug
難度 4/5 3-5 天 新手友好度 48/100
microsoft/PowerAppsCodeApps#461 ·
-
bug
難度 5/5 一週以上 新手友好度 28/100
microsoft/PowerAppsCodeApps#460 · 3 則留言 ·
查看 microsoft/PowerAppsCodeApps 的全部 Issue
相似的 Issue
-
priority: P2
難度 2/5 1-3 小時 新手友好度 78/100
-
難度 2/5 1-3 小時 新手友好度 65/100
prime-radiant-inc/evener#3291 ·
維護者通常 1 天內回覆
-
accessibility bug revealjs
難度 2/5 1-3 小時 新手友好度 84/100
quarto-dev/quarto-cli#14961 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 90/100
supabase/agent-skills#614 ·
-
Content
難度 2/5 1-3 小時 新手友好度 68/100
RunestoneInteractive/rs#1559 · 1 則留言 ·
維護者通常 2 天內回覆