Client: Error unboxing chat message

[ajsb85]

Error unboxing chat message: You are not a member of this team (error 2623)

[ajsb85]

[ajsb85]

[ajsb85]

[maxtaco]

Cc @mmaxim does this look right?

[mmaxim]

Is this still a problem, if so, can you try keybase db nuke?

[ajsb85]

keybase db nuke done

Still the same problem.
I had this problem from a lot of months ago.
I was trying these days to install and use keybase to see if it already fixed.

Regards.

[mmaxim]

What version of Keybase are you running, can you send a log?

[mmaxim]

keybase log send to send a log

[mmaxim]

Actually I think I see what is going on here. @maxtaco this might end up being a little tricky. What has happened is the following:

1.) cyrildamas started an implicit team chat with ajsb85 when ajsb85 had no PUK.
2.) cyrildamas takes all their devices offline. ajsb85 comes back and wants to chat.
3.) ajsb85 just sees errors since there is no one online to sign his invite into the team.

[ajsb85]

my log id: a6e93ab971e0e898037f841c

[ajsb85]

keybase version 1.0.40-20180205105125+493a528

[mmaxim]

@ajsb85 you can probably get this situation fixed if cyrildamas starts a Keybase client again.

[ajsb85]

We are coworkers.
And this issue is from many months ago.
I reset my keybase and still the same problem.

[ajsb85]

He shared a new information with me recently.
Could you help us? @cyrildamas

[ajsb85]

[mmaxim]

Does he have a device online?

[ajsb85]

He opened the client and sent again a message 2 minutes ago.

[maxtaco]

Can he do keybase log send?

[ajsb85]

@cyrildamas please exec keybase log send

[ajsb85]

We are using this thread as chat 🤣

[cyrildamas]

my log ID 053857c38194803a1b9db01c

[ajsb85]

[mmaxim]

@cyrildamas sorry to do this to you, but could you log send one more time?

[ajsb85]

[cyrildamas]

[cyrildamas]

Success! Your log ID is: 6d029d85d1ec62af4bbdad1c

[ajsb85]

Success! Your log ID is:

509a813510174a3b062f4d1c

[cyrildamas]

my MacOS client Version 1.0.40-20180205183337+269845275

[maxtaco]

@ajsb85 we need to be better about communicating this, but by resetting your account, you made things worse. In general, reset accounts are challenging to handle, and have more bugs than non-reset accounts.

[mmaxim]

So I made a change on the server which may have fixed this for you all. Both sides of the chat should now advertise ajsb85 as being reset, and cyrildamas should have the option to "re-add" him into the conversation.

[ajsb85]

[mmaxim]

Yep that is how it should show up for you, cyrildamas should be able to let you back in.

[cyrildamas]

when i "Let them In" =

[mmaxim]

Sorry about that guys, this is a bug in the client adding back a reset user that did not have a per user key when the conversation was created. I am going to try and fix it right now.

[mmaxim]

This should be fixed in the latest releases of the clients, let me know if it is still a problem.

[ajsb85]

[mmaxim]

Did you try to create a new conversation with the same person that you have an existing conversation you are locked out from? He needs to let you back into the original one with a new client.

[ajsb85]

[mmaxim]

Great!

[wesinator]

I'm experiencing a similar issue on macOS
Version 2.12.6-20190103193723+07470de987 (2.12.6-20190103193723+07470de987)

I started being followed by team members and was shared chats before I was a member of the team. The chats shared with me display Unable to decrypt chat message: You are not a member of this team (error 2623)

After running keybase team request-access and getting welcomed to the team, I still see the unable to decrypt error message on the most recent messages, but I can read older messages from over a month ago.

I also see this error message in a direct conversation with a user on my team, making me unable to read the chats they sent me.

I don't have any keys set up yet on my account, but if that were the issue, I would think it should show a different error message, and I wouldn't be able to read older messages.