pa CLI cannot reach default-prefixed environments (DNS ENOTFOUND); Dataverse connector rejects current as organization in default env
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 22/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- nodejs, powershell, typescript
调研方向
The payload names no file in this repository. The first failure is in the pa app init environment lookup in @microsoft/power-apps-cli 1.2.0, which builds the per-environment hostname without the default-environment prefix. Reproduce with pa app init -e <default-env-id> and compare the host it requests with the one that resolves. The second is the ListRecordsWithOrganization call with organization "current" in the Dataverse connector. Done means the default environment resolves and the connector accepts "current" or documents that it does not.
由索引模型根据 Issue 内容生成。
描述
Issue 1: pa CLI network failures — wrong per-env hostname + IPv6
CLI: @microsoft/power-apps-cli 1.2.0 (global pa and npx --no-install power-apps, identical result), Node v24.18.1, Windows.
Repro (a) — wrong hostname for default env:
pa app init -n "my-app" -e c3df2a3c-e602-4ef6-b29d-3bac03b3991c
Fails after ~50ms:
Network request failed for GET https://c3df2a3ce6024ef6b29d3bac03b399.1c.environment.api.powerplatform.com/powerapps/environment?api-version=1&...
Details: getaddrinfo ENOTFOUND ... Non-existent domain
The correct host for this (default) environment carries the env prefix: defaultc3df2a3c...1c.environment.api.powerplatform.com (verified resolving, v4+v6). The CLI omits the prefix. Verified the constructed name is genuinely NXDOMAIN, not a local DNS issue. pa app init against a normal env in the same tenant works. (Worked around creation via deprecated pac code init, whose endpoints resolve correctly.)
Repro (b) — pa app push intermittently fails, IPv4 fixes it:
pa app push sometimes fails with network errors. Forcing IPv4 makes it reliable:
$env:NODE_OPTIONS="--dns-result-order=ipv4first"
pa app push # consistently succeeds
DNS returns IPv6 (2603:1061:...) first for the API endpoints and the IPv6 path appears broken from this network — Node tries IPv6 first by default but the CLI surfaces a hard failure instead of falling back.
Expected: CLI resolves the environment endpoint (with prefix) before calling it, and either prefers IPv4 or retries across address families instead of hard-failing.
Issue 2: "current" as Dataverse connector organization fails only in default env
MicrosoftDataverseService.ListRecordsWithOrganization("current", "accounts", ...) fails at the connector runtime only in the default environment:
{"Message":"Invalid organization URL '' provided.","OperationId":"ListRecordsWithOrganization", ...}
Verified matrix (same call, same connector shared_commondataserviceforapps):
| App | Env | "current" |
Full org URL |
|---|---|---|---|
| Solution-imported app | normal env | ok | ok |
| Solution-imported app | default env | fails | ok |
| Direct-created app (fresh portal connection, no solution involved) | default env | fails | ok |
Just a small observation from the default environment. The official connector reference documents the parameter only as Environment | organization | True | string | Choose an environment — no accepted value format, no "current" keyword anywhere. On my end I worked around it with plain ListRecords, which binds to the connection's own environment with no organization parameter.
Versions: @microsoft/power-apps 1.5.0, @microsoft/power-apps-cli 1.2.0, @microsoft/power-apps-vite 1.0.2.
- 主要语言
- TypeScript
- 星标
- 513
- 派生
- 143
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 11
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/PowerAppsCodeApps 的其他 Issue
-
[Bug] shared_odbc with on-prem fails pointing to placeholder URL可能已有人在做 @tonystevenj 于 3 天前认领。 未关闭bug
难度 4/5 3-5 天 新手友好度 45/100
microsoft/PowerAppsCodeApps#465 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
[Bug] Power App Code App doesn't run in China 21V cloud even with the toggle enabled可能已有人在做 @tonystevenj 于 5 天前认领。 未关闭bug product team investigating
难度 4/5 3-5 天 新手友好度 35/100
microsoft/PowerAppsCodeApps#463 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 48/100
microsoft/PowerAppsCodeApps#461 ·
维护者通常 1 天内回复
-
bug
难度 5/5 一周以上 新手友好度 28/100
microsoft/PowerAppsCodeApps#460 · 3 条评论 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 48/100
microsoft/PowerAppsCodeApps#459 ·
维护者通常 1 天内回复
查看 microsoft/PowerAppsCodeApps 的全部 Issue
相似的 Issue
-
fix(frontend): correct VITE_IS_DEVELPOMENT typo in shared/app.ts and align dev environment flags未关闭
难度 2/5 1-3 小时 新手友好度 75/100
vicharanashala/ajrasakha#1439 ·
维护者通常 1 天内回复
-
approved check:passed streams:add
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
backnotprop/plannotator#1932 ·
维护者通常 1 天内回复
-
难度 2/5 半天 新手友好度 62/100
ibm-granite/granite.build#504 ·
维护者通常 2 天内回复
-
reproduced
难度 2/5 1-3 小时 新手友好度 82/100
anomalyco/opencode#55676 · 1 条评论 ·
维护者通常 1 天内回复