question-mark
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.

CypressError: Timed out retrying: coordsHistory must be at least 2 sets of coords

See original GitHub issue
  • Operating System: Windows 10
  • Cypress Version: 1.0.3
  • Browser Version: 62

Is this a Feature or Bug?

Bug

Current behavior:

When running my tests I try to trigger a dragDrop event. Even when passing { force: true }, this exception is still encountered. This only happens on headless test runs. It worked fine in the browser.

Desired behavior:

Ideally this exception wouldn’t be thrown. Not sure why it’s happening.

How to reproduce:

This happened using anglar-file-upload code in a private respository. Not sure the best means to reproduce.

Test code:

    it('Allows for ---- Upload', function () {
      cy.get('.my-drop-zone').first()
        .trigger('dragover', this.dropEvent)
        .should('have.class', 'nv-file-over')
        .trigger('drop', this.dropEvent, { force: true }) // this is where it fails even with force true
    })
  })

Additional Info (images, stack traces, etc)

image

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:7 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
chrisbreidingcommented, Nov 14, 2017

It’s possible it’s trigger('dragover') that causes the error. Does the error still occur if you put { force: true } on that too?

0reactions
afameecommented, Jul 15, 2019

I am experiencing similar issues in my own test. The frustrating part is that its not consistent.

gitMultiClickCoordsIssue

Here is the piece of code:

andValidateMvrReport(last, valid){

    cy.get('a#Tab_DataReports').should('be.visible').then(dr => {

      cy.wrap(dr).click();

      cy.get("img[src='img/expand.gif']").click({ multiple: true, timeout: 16000 })

      cy.get("tr[id^='rowInProcess']")
      .find('td').contains('Get MVR for '+last).as('currrow').then(() => {

        cy.get('@currrow').parent().prev('tr').as('therow')
        
        cy.get('@therow').within(() => {
          cy.get("td[id$='ResultCd']").should('have.text', valid);
        })
      })
    })
    return this;
  }
  • Operating System: Windows 10 Pro
    
  • Cypress Version: 3.3.2
    
Read more comments on GitHub >

github_iconTop Results From Across the Web

Timed out retrying: coordsHistory must be at least 2 sets of ...
The error message is definitely misleading. It should say something like 'Timed out attempting to click multiple elements'. The coordsHistory ...
Read more >
Error while executing test on Cypress--Timed out retrying after ...
Error while executing test on Cypress--Timed out retrying after 4050ms: coordsHistory must be at least 2 sets of coords.
Read more >
coordsHistory must be at least 2 sets of coords - Bountysource
CypressError: Timed out retrying: coordsHistory must be at least 2 sets of coords · Operating System: Windows 10 · Cypress Version: 1.0.3 ·...
Read more >
Bug #931: CypressError: Timed out retrying: coordsHistory ...
CypressError : Timed out retrying: coordsHistory must be at least 2 sets of coords ; Start date: 08/14/2020 ; Due date: ; %...
Read more >
cypress-io/cypress - Gitter
We added a debugger and in Chrome 79 we're starting to get this error when the click occurs "coordsHistory must be at least...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found