Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#472 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
nodejs, powershell, typescript
Área
api, cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
516
Forks
145
Merge medio
23 h 41 min
PR fusionados (30 d)
18

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/PowerAppsCodeApps

Todos los issues de microsoft/PowerAppsCodeApps

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.