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.

Unexpected token in JSON

See original GitHub issue

Current behavior

Occasionally hitting this issue when running on MacOS 12, Node v14.20.0 and Chrome 103 / Firefox 103.

================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        10.3.1                                                                         │
  │ Browser:        Custom Chrome 103                                                              │
  │ Node Version:   v14.20.0 (/Users/chef/payload/bundle/bundle/node)                              │
  │ Specs:          20 found (todo.cy.js, actions.cy.js, aliasing.cy.js, assertions.cy.js, connect │
  │                 ors.cy.js, cookies.cy.js, cypress_api.cy.js, files.cy.js, local_storage.cy.js, │
  │                  location.cy.js, misc.cy.js, navigation.cy.js, network_requests.cy.js, queryin │
  │                 g.cy.js, spies_stubs_cl...)                                                    │
  │ Searched:       **/*cy.js                                                                      │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘


────────────────────────────────────────────────────────────────────────────────────────────────────
                                                                                                    
  Running:  todo.cy.js                                                                     (1 of 20)
Unexpected token < in JSON at position 0
SyntaxError: Unexpected token < in JSON at position 0
    at JSON.parse (<anonymous>:null:null)
    at /Users/chef/payload/bundle/bundle/Cache/10.3.1/Cypress.app/Contents/Resources/app/node_modules/chrome-remote-interface/lib/devtools.js:121:33
    at IncomingMessage.<anonymous> (/Users/chef/payload/bundle/bundle/Cache/10.3.1/Cypress.app/Contents/Resources/app/node_modules/chrome-remote-interface/lib/external-request.js:32:17)
    at IncomingMessage.emit (node:events:402:35)
    at IncomingMessage.emit (node:domain:475:12)
    at endReadableNT (node:internal/streams/readable:1343:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

Desired behavior

Error should not occur.

Test code to reproduce

Cypress kitchensink example.

Cypress Version

10.3.1

Other

No response

Issue Analytics

State:
Created a year ago
Comments:14 (3 by maintainers)

Top GitHub Comments

1reaction

rockindahizzycommented, Aug 11, 2022

Hey @alexplischke,

There are few different logs that might provide useful information. Unfortunately, I can’t reproduce this. I would greatly appreciate it if you had the time to try to grab the logs in the failure scenario.

DEBUG=cypress:server:browsers:cri-client*,cypress-verbose:server:browsers:cri-client*,cypress:server:browsers:browser-cri-client npx cypress run

0reactions

nagash77commented, Aug 22, 2022

Reopening so we can use this ticket to track the status of updating the get-port library once we have a minimum node version that allows us to require node >12.20. Going to route this ticket to the E2E team for prioritization in their backlog.