On my Windows client, a lot of groups are corrupted and they show a Malformed add member commit error.
I collected the logs, found similar sections, identified common scenarios.
[??????????.???|????|conversationrepository.cpp:2559] [Account **] [Conversation *****] Unable to get diff stats
[??????????.???|????|conversationrepository.cpp:2881] [Account **] [Conversation *****] Validate commit *****
The above content usually appears before the error, where the second line may appear many times with different commits, and sometimes the content of the first line before the last of them.
[??????????.???|????|conversationrepository.cpp:2559] [Account **] [Conversation *****] Unable to get diff stats
[??????????.???|????|conversationrepository.cpp:2747] [Account **] [Conversation *****] Malformed add commit *****. Please check you use the latest version of Jami, or that your contact is not doing unwanted stuff.
[??????????.???|????|conversation.cpp :1776] [Account **] [Conversation *****] Unable to validate history with ********
This is the core of where the error lies. The mentioned commits look normal.
[??????????.???|????|conversation.cpp :1912] Successfully fetched from device ******** but didn't receive expected commit *****
[??????????.???|????|conversation_module.cpp :676 ] [Account **] [Conversation *****] Unable to fetch new commit from ********, other peer may be disconnected
[??????????.???|????|conversation_module.cpp :680 ] [Account **] [Conversation *****] Relaunch sync with ********
At one time, these appear after the error, referring to a different commit than the previous one.
Should I merge commits manually?