luizluca
commented
5 years ago It might be related to #9 as it could be some leftovers from old telepathy account (although here I'm using the same phone number)
Closed luizluca closed 5 years ago
luizluca
commented
5 years ago It might be related to #9 as it could be some leftovers from old telepathy account (although here I'm using the same phone number)
Kaffeine
commented
5 years ago The last line says that "AUTH_KEY_UNREGISTERED", so telepathy-morse indeed picked up the old key that is not assigned to any account on the server side. Right after the debug message, TelegramQt emits signal authorizationErrorReceived(), that is connected to onAuthErrorReceived in morse. The signal handler is expected to initiate connection without the previous session data.
I don't see how Morse can stuck in such state, but I can add a code to cleanup session data as we got the signal that the key is not valid. It would be better to drop only the auth key and keep the connection state data to avoid client from repeated download of the already received messages but it would be hard to do with the current session data structure.
At the meantime you can remove the old key manually. The file is located in cache directory:
rm ~/.cache/telepathy-morse/secrets/<phone_number>
If this is the only account, then you can safely remote the entire directory:
rm -rf ~/.cache/telepathy-morse
luizluca
commented
5 years ago I removed the secrets and now it connects correctly. Thanks!
I used an old morse version but today I installed git version b2de385. I'm behind an HTTP proxy (env vars are correct). It seems to be using my proxy settings nicely (no morse proxy parameters set). My GUI client is empathy but I mostly tested with mc-tool.
It looks like it goes from Connecting to Authenticated without actually being authenticated.
I got no authentication code on phone or client (I'm connected in a web client).
I don't know if it is trying to reuse an old expired activation key (from previous tests) or the state machine got confused and jumped directly into ConnectionStateAuthenticated without actually being authenticated.