New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Signal on macOS often unlinks #6856
Comments
Hi! Sorry this is happening for you. Can you please provide debug logs? On desktop that's Menu -> View -> Debug Log. |
Hi, this is my debug log: |
@Sislik42 Try uninstalling Signal on your macOS and then reinstalling it. This may help fix errors or check the activated device sessions in the Signal app on the iPhone to make sure that the macOS device is still connected. |
@Ismail-Benali @Sislik42 I wouldn't recommend an uninstall/reinstall cycle. I would recommend going to your primary device, to the Settings area, then the Linked Devices screen. That will tell you how recently the linked device in question has been used - if it hasn't been used recently, then that's the explanation for it being unlinked. We've recently added popup reminders to Android and iOS to let you know when a device is soon to be auto-unlinked, hopefully that helps! |
@scottnonnenberg-signal so it's not a bug, but it's a feature? :-) Thank you for explaining. I don't use Signal on my Mac very often, so it's highly possible that it was unlinked automatically by design. I understand that it's unliked automatically for security reasons, but this computer is a Mac Studio which stands only on my desk and I'm the only user there, so risk is basically none :-) |
Using a supported version?
Overall summary
Signal on macOS often unlinks and then I can§t use it anymore, until I link it again using app on iPhone
Steps to reproduce
Expected result
Signal never unlink from macOS app
Actual result
Signal sometimes unlinks from macOS app.
Screenshots
No response
Signal version
7.4.0
Operating system
macOS 14.4.1
Version of Signal on your phone
Unknown, I don't have my iPhone with me know
Link to debug log
No response
The text was updated successfully, but these errors were encountered: