Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

🐛 BUG: Received a malformed response from the API

See original GitHub issue

What version of `Wrangler` are you using?

2.0.8

What operating system are you using?

Mac

Describe the Bug

I can’t publish my project anymore (which I could publish yesterday just fine).

❯ wrangler publish --env staging
 ⛅️ wrangler 2.0.8
-------------------
Your worker has access to the following bindings:
- Vars:
  - ENVIRONMENT: "staging"

✘ [ERROR] Received a malformed response from the API

  {
    "result": {
      "id": "front-staging",
      "etag": "c2bc4c316edc5f156011be2cafb1a0ba8e2e6584c277... (length = 2809573)

  PUT /accounts/d7c7e62dcb0e66.......7b90d86b10/workers/scripts/front-staging -> 200 OK

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/wrangler2/issues/new/choose

EDIT: Correction, it seems the project was published, even though Wrangler gives me an error.

Issue Analytics

State:
Created a year ago
Comments:13 (8 by maintainers)

Top GitHub Comments

4reactions

threepointonecommented, Jun 13, 2022

We have a fix rolling out on the api side (hopefully this week?), and a wrangler pr that leverages that fix (https://github.com/cloudflare/wrangler2/pull/1248) which we’ll land soon after

0reactions

threepointonecommented, Jun 15, 2022

I believe the escaping bug has been fixed on the api end, and the additional fix to not include it given the excludeScript query params will be rolled out soon. So I’m going to close this. Thanks everyone for reporting!