Hacktoberfest 2026：維護者為十月標記出來的 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 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
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 小時
30 天內合併 PR
163

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

Shopify/cli 的其他 Issue

查看 Shopify/cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。