Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#8,906 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 2 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
30/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
authentication, cli

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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
主要言語
TypeScript
スター
757
フォーク
294
平均マージ
2日 20時間
マージ済み PR（30日）
163

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Shopify/cli のほかの issue

Shopify/cli の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。