Describe the bug
When I launch the Mostro client after a long period of inactivity, sometimes it fails to connect to the main instance or any other instance. Attempting to change the instance or reload the relay information does not work. However, simply restarting the application resolves the issue completely, and the connection is established immediately on the first try.
To Reproduce
Steps to reproduce the behavior:
- Leave the Mostro client inactive or closed for a long period.
- Launch the application.
- Observe that it fails to connect to the main instance or any other instances.
- Attempt to change the instance or reload the relay information (notice that it does not fix the connection).
- Restart the application.
- Notice that the connection is now established instantly.
Expected behavior
The application should successfully connect to the selected instance upon the initial launch, even after a long period of inactivity, without requiring a manual restart of the app.
Screenshots
I have attached a video demonstrating the behavior.
[Añade aquí el enlace o sube el archivo de tu video]
Desktop (please complete the following information):
- OS: Linux Mint
- Browser: N/A (Desktop App)
- Version: 1.2.3
Smartphone (please complete the following information):
- Device: OnePlus 13T
- OS: Android
- Browser: N/A (Mobile App)
- Version: 1.2.3
Additional context
The issue is cross-platform, as it happens exactly the same way on both Linux and Android. It seems that once the connection fails initially, the internal state cannot be recovered by manually refreshing relays or changing instances, requiring a full application restart to restore connectivity.
Describe the bug
When I launch the Mostro client after a long period of inactivity, sometimes it fails to connect to the main instance or any other instance. Attempting to change the instance or reload the relay information does not work. However, simply restarting the application resolves the issue completely, and the connection is established immediately on the first try.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The application should successfully connect to the selected instance upon the initial launch, even after a long period of inactivity, without requiring a manual restart of the app.
Screenshots
I have attached a video demonstrating the behavior.
[Añade aquí el enlace o sube el archivo de tu video]
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The issue is cross-platform, as it happens exactly the same way on both Linux and Android. It seems that once the connection fails initially, the internal state cannot be recovered by manually refreshing relays or changing instances, requiring a full application restart to restore connectivity.