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

[Bug]: app-logs poll returns HTTP 400 "Malformed JWT" — `shopify app dev` loops "Error while polling app logs" (CLI 4.9.4)

Offen
  • Stimmt etwas nicht?
#8,906 0 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
authentication, cli

Rechercherichtung

Start in the app-logs poller's error handler (onUnknownError), which drops the status and body before printing "Error while polling app logs.", and in the request builder that sets the authorization and X-Shopify-Access-Token headers for app_logs/poll. A reasonable first step is to surface the HTTP status and response body in that error output and check it with a test or a mocked 400 response. The root cause lies server-side and is under investigation by Shopify, so the work is not to fix the JWT.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Summary

With an app that has a Function extension, shopify app dev starts the app-logs poller (as designed), but every poll fails and the app-logs panel loops forever:

app-logs │ Error while polling app logs.
app-logs │ Retrying in 5 seconds.

The underlying request returns HTTP 400 {"errors":["Malformed JWT"]}. The CLI never shows the status or body, so the failure is undiagnosable without patching the CLI.

Expected behavior

shopify app dev streams Function run logs to the terminal under the app-logs prefix.

Actual behavior

Every app_logs/poll request fails from the first request to the end of the session, repeating every 5 seconds. shopify app logs -s <dev-store> reproduces the identical failure standalone, so it is not specific to app dev.

Note: only apps that contain a Function extension poll app logs at all (allExtensions.some(isFunctionExtension) gates the poller), so apps without a Function extension are unaffected and will not show this.

Reproduction
  1. Use an app that contains a Function extension (e.g. any type = "function" extension in shopify.extension.toml).
  2. Link a development store.
  3. Run shopify app dev (or shopify app logs -s <dev-store>).
  4. Observe the loop.
Evidence (captured on CLI 4.9.4)

AppLogsSubscribe (App Management API) succeeds and returns a jwtToken. The subsequent poll is then rejected:

  • Request: GET https://app.shopify.com/app_management/unstable/organizations/<org-id>/app_logs/poll
    • headers sent (per the CLI's own builder): authorization: Bearer <jwt> and X-Shopify-Access-Token: Bearer <jwt>
  • Response: HTTP 400
  • Body: {"errors":["Malformed JWT"]}

The JWT is fresh (30 minutes from expires_at) and its payload carries no organization claim:

{"shop_ids":[<id>],"app_id":<id>,"api_key":"<redacted>","user_id":"<redacted>","expires_at":<future>}

The poll endpoint is organization-scoped, and the token contains no organization claim. That mismatch is one hypothesis; it is also consistent with a signing/secret mismatch on the server side. Either way the minted subscription token is not accepted by the poll endpoint for any shop or organization.

CLI defect (separate, makes this hard to diagnose)

The poller's error handler drops the status code and response body before printing Error while polling app logs. (onUnknownError). --verbose shows the request but not the response, so the 400 + Malformed JWT only surfaces if the CLI is patched.

Environment
  • Shopify CLI 4.9.4 (Homebrew), macOS (arm64)
  • Node 26.11.1
  • App has exactly one function extension
  • organizationId resolves correctly for this app (appByKey returns it), so this is not a missing-organization problem
Notes
Vorherrschende Sprache
TypeScript
Sterne
757
Forks
294
Ø Merge
4 T. 12 Std.
Gemergte PRs (30 T.)
175

Entwicklungsumgebung

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 Shopify/cli

Alle Issues in Shopify/cli

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

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