You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2022. It is now read-only.
Thank you for working on this. You absolutely rock!
The issue:
I run the server on system boot (added to 'Login Items' with auto-login).
On the latest version, 3.4.1, AirMessage will often start in an error state. Right-clicking on the icon gives the error "Communications error" and there's a Retry button. 100% of the time clicking on Retry will start the server successfully.
So my suggestion is: can/would you add a built-in timer that automatically reattempts to start the server on this error? That'd be extremely helpful and save me from having to remote into the machine only to click Retry.
Thanks! :)
The text was updated successfully, but these errors were encountered:
Thanks for the report, I can definitely see how this would be frustrating. The app does automatically try to reconnect when the internet can't be reached, but not when a communications error occurs - I'll see if I can fix this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Thank you for working on this. You absolutely rock!
The issue:
I run the server on system boot (added to 'Login Items' with auto-login).
On the latest version, 3.4.1, AirMessage will often start in an error state. Right-clicking on the icon gives the error "Communications error" and there's a Retry button. 100% of the time clicking on Retry will start the server successfully.
So my suggestion is: can/would you add a built-in timer that automatically reattempts to start the server on this error? That'd be extremely helpful and save me from having to remote into the machine only to click Retry.
Thanks! :)
The text was updated successfully, but these errors were encountered: