We should handle rejected promise without error object better

[bahmutov]

Cypress 3.1.5

PR with bug reproduction cypress-io/cypress-test-tiny#35

spec

/// <reference types="cypress" />
describe('page', () => {
  it('fails', () => {
    cy.wrap(null).then(Cypress.Promise.reject)
  })
})

When running shows our error

The stack shows where the error is coming from - we are checking err. property, but there is no err

[jennifer-shehane]

This is still happening in Cypress version 3.4.0

[jennifer-shehane]

This fails with a new error msg in 4.5.0+, no stack trace.

[alexey-sh]

It's sad to see that cypress doesn't support so basic features... Maybe it will be added in future. How many years should it take?

[cypress-app-bot]

This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided.

[alexey-sh]

I bet the issue is going to be closed due to poor support

[nagash77]

@alexey-sh we are trying to improve our support channels as we scale as a company. This issue was incorrectly picked up by the stale bot. Do not worry, it is not going to be closed at this point. Thank you for your kind words and continued support.

[bahmutov]

The automatic stale bot should skip any issue reported by me, just saying