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
iMessage bridge is no longer sending or receiving new messages. I am working on diagnosing why, and I want to collect as much info from others as possible to work towards a fix. This will need to come from the community as it has been abandoned by Beeper
The text was updated successfully, but these errors were encountered:
When I set up this bridge after restarting the process I stopped receiving messages but was still able to send messages albeit with a warning:
Is this the bug or is there a newly arising issue?
I could help at the very least provide some logs or try to debug, main issue is I don't really have iMessage contacts to test it with and Apple being Apple I can't just create an alt account.
When I set up this bridge after restarting the process I stopped receiving messages but was still able to send messages albeit with a warning:
Is this the bug or is there a newly arising issue?
I could help at the very least provide some logs or try to debug, main issue is I don't really have iMessage contacts to test it with and Apple being Apple I can't just create an alt account.
how do you get logs like that? i can help you test if you need someone with imessage.
I used the bridge actively until it stopped working at some point between Feb 9-11th. Tried deleting and re-adding the bridge, which didn't work. What is weird though is that Beeper seems to think that everything is working just fine. I never got an error when setting it back up with a Mac nor when I try to send a message and it never delivers.
iMessage bridge is no longer sending or receiving new messages. I am working on diagnosing why, and I want to collect as much info from others as possible to work towards a fix. This will need to come from the community as it has been abandoned by Beeper
The text was updated successfully, but these errors were encountered: