Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with synchronization of messages #2188

Closed
grzegorj opened this issue Jun 8, 2024 · 3 comments
Closed

Problem with synchronization of messages #2188

grzegorj opened this issue Jun 8, 2024 · 3 comments

Comments

@grzegorj
Copy link

grzegorj commented Jun 8, 2024

After a new installation of Caprine, messages newer than of the end of March 2024 do not show up. Instead, you can see a message: “Some messages are missing. Synchronize now.” (translated back from my local language into English)
“Synchronize now” looks like a hyperlink. But if you click it, nothing happens. Especially, no lacking messages re-appear.

If a new message shows in this conversation (not important, from me or from the person I am talking with), the previously seen message “Some messages are missing. Synchronize now.” is not seen any longer. Now the lacking messages are still invisible, and there is no way to make them appear again.

The messages in question are coded. The original client (Messenger) has no problems with bringing them back, so it must be not impossible. It is Caprine which has problem with them. And which is more, it seems to offer a function (“Synchronize now”) which does not work at all. So, what is it for?


Caprine 2.60.1
Electron 29.0.1
win32 10.0.22000
Locale: pl

@triforcely
Copy link

#2167

@mquevill mquevill closed this as not planned Won't fix, can't repro, duplicate, stale Jun 18, 2024
@logiclrd
Copy link

logiclrd commented Jul 8, 2024

"Not planned"?? If anything, this should have been closed as a duplicate...

@mquevill
Copy link
Collaborator

mquevill commented Jul 8, 2024

"Not planned"?? If anything, this should have been closed as a duplicate...

It is closed as a duplicate. If you mouse over the "not planned" status, GitHub's help text is "Won't fix, can't repro, duplicate, stale". The only built-in options in GitHub are either "Close as completed" or "Close as not planned".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants