alttester / alttester/AltTester-Unity-SDK

[WebSocket] [C# Driver] The error regarding the inability of connection to AltServer of the tests is different depending on the connectTimeout

Ouverte
#1,463 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
bug no version triaged
Langage dominant
C#
Étoiles
121
Forks
24
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

## Steps to reproduce

1. Open the AltTester-Unity-SDK project in Unity
2. Create an AltTest file under an Editor folder
3. Open it in IDE and add a `connectTimeout` parameter to the altDriver of a value bigger than 23 seconds
4. Run the AltTest
5. Modify the connectTimout value into a value smaller than 24 seconds
6. Run the AltTest

## Actual result

### AR

4. The `System.InvalidOperationException : A series of reconnecting has failed` error is triggered
5. The `ConnectionException : Connection closed by AltServer with reason: An exception has occurred while attempting to connect..` is triggered

The error is different depending on connectTimeout value.
### Additional info

❗ When the `ConnectionException` is triggered (as in case of Java and Python drivers) the message displayed is different than the message from Java and Python (`Connection closed by AltServer with reason: An exception has occurred while attempting to connect..` instead of `Failed to connect to AltTester on host: 127.0.0.1 port: 13000`).
Setup:
- AltTester-UInity-SDK project from latest dev branch (04.01.2024)
## Expected result

### ER

The error triggered in this situation should be `ConnectionException` and it should be independent of `connectTimeout`. Also the message of the error should be constant with the messages displayed by `Java` and `Python` drivers
### Additional info

## Testability

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.