The bridge does not automatically reregister IDS upon receipt of a 6005 error
Technophilus opened this issue · comments
Several hours after registering my phone number on the bridge, I get a notification on my iPhone (that beepserv runs on) that iMessage is now being used on another device. Then, I can no longer issue commands such as resolve-identifier and the bridge bot shows a 6005 error. This is resolved with the command reregister-ids, but this should be automated to ensure reliability of the bridge. Additionally, it seems like it should be reregistering based on what is in the log. The log is attached to this issue.
See this line specifically:
2023-12-22T22:37:13Z WRN Profile needs refresh, not re-registering event_id=$RvuHaJgPuktSepAbNXTzuqCk5h-1nkx3sN4pVip1N2I mx_command=resolve-identifier own_handle=tel:+{REDACTED my phone number} profile_id=D:{REDACTED profile ID} room_id=!dbfDZzZsPNkJADKpqp:{REDACTED matrix server} sender=@tech:{REDACTED matrix server}
This issue is resolved when the bridge no longer shows 6005 errors solely due to a reregistration being needed, because the bridge will have done it automatically.
Update: it seems that this doesn't actually work. The bridge was just caching responses and was still unauthenticated. I'll open up a new issue once I have enough figured out to debug it.