Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

pa CLI cannot reach default-prefixed environments (DNS ENOTFOUND); Dataverse connector rejects current as organization in default env

Offen
  • Stimmt etwas nicht?
#472 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
22/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
nodejs, powershell, typescript
Bereich
api, cli

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
513
Forks
143
Ø Merge
1 T. 1 Std.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/PowerAppsCodeApps

Alle Issues in microsoft/PowerAppsCodeApps

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.