In certain cases, the app can display cryptic error messages that are not very helpful - to our users, or to us.

Failed Upload error messages should display after the "Uploaded Cloud Artifacts" section.

Failed Recording error messages should display before the "Uploading Cloud Artifacts" section.

Failed Uploads, Cause: HTTP Status Code 403, 404, 413

Source issues:

• https://github.com/cypress-io/cypress-services/issues/7722 (403)
• https://github.com/cypress-io/cypress-services/issues/7732 (404)
• https://github.com/cypress-io/cypress-services/issues/7723 (413)

Acceptance: surface more informative error:

Unable to upload this spec's Test Replay recording due to an error during the upload process:

$URL responded with HTTP $CODE, $DESCRIPTION

Failed Uploads, Cause: Network Error
Socket Hangup, Proxy Error, ECONNRESET are likely caused by a network or network configuration error.
Acceptance: surface a more informative error; solution: fix network configuration

Acceptance: surface a more informative error:

Unable to upload this spec's Test Replay recording due to a network error during the upload process: $ERR

Please verify your network configuration for accessing $URL.

Source issues:

• Protocol: [upload] "socket hang up" error when uploading replay test in Cypress Cloud #28004
• https://github.com/cypress-io/cypress-services/issues/7731
• https://github.com/cypress-io/cypress-services/issues/7566

Failed Uploads, Cause: runtime error
Sometimes we encounter an "cannot read .pipes of undefined" error during upload. This is being thrown from ReadableStream with an unknown cause.
Acceptance: Display an error:

Unable to upload this spec's Test Replay recording. An error occurred while trying to read $FILENAME:

$ERR

Failed Initialization
Sometimes, we fail to initialize Protocol in a way that does not throw a terminal error. This results in either an undefined archivePath on ProtocolManager.ts in app (Error: no test data recorded). Sometimes, an inability to open the sqlite file in beforeSpec results on a terminal error (SqliteError: Unable to open database file). Messaging on both can be improved:

Unable to initialize Test Replay recording for this spec (TBD - determine what is failing, and throw an appropriate error).

Unable to initialize Test Replay recording for this spec. (TBD: should we display the path to the sqlite file we were trying to open?)

Failed Recording
An unknown error, ftruncate error seems to be thrown from indexed-tarfile when we append, sometimes.
Acceptance: Display a more informative error; potential solution: increase available disk space

Unable to add one or more Test Replay assets to the recording. Please verify disk space availability.

SqliteError: Database or Disk is Full can be encountered whenever we write to the database, or close it.
Acceptance: Display a more informative error; solution: increase available disk space

Unable to add one or more Test Replay events to the recording. Please verify disk space availability.