BlueBubblesApp
Missing Messages
It appears sometimes I receive an iMessage and BlueBubbles does not process it.
Logs are pretty sparse at the time of one example this morning, saying only
2024-10-11 08:03:39.579][debug] [IMessageListener] Detected change in database files: /Users/.../Library/Messages/chat.db
[2024-10-11 08:03:39.587][debug] [IMessageListener] Not processing DB change: 1728599114325.8855 <= 1728607377397.4792
I assume you're on the beta... and if you are, I believe that this PR should fix it: https://github.com/BlueBubblesApp/bluebubbles-server/pull/696
so it may be fixed, just the fix hasn't been released yet. If you are concerned, go back to stable for the time being.
fwiw, that log doesn't necessarily mean it missed anything, but it could be
I assume you're on the beta... and if you are, I believe that this PR should fix it: https://github.com/BlueBubblesApp/bluebubbles-server/pull/696
No, server 1.9.7.
fwiw, that log doesn't necessarily mean it missed anything, but it could be
Mmm, okay. Given there was a message at that time and no other logs in BB I assumed that the issue was on the BB end, though its possible that isn't the case (the client here is a matrix bridge).
Oops, sorry, duh. Sonoma 14.7 (upgraded from several previous OS'), amd64.
Should be fixed in https://github.com/BlueBubblesApp/bluebubbles-server/pull/696
Yay thanks for the release! Just upgraded to v1.9.8 and, sadly, it seems this issue has gotten worse. Now there are no logs at all for most messages and they're simply missed :(.
Yay thanks for the release! Just upgraded to v1.9.8 and, sadly, it seems this issue has gotten worse. Now there are no logs at all for most messages and they're simply missed :(.
Can you go to https://time.is on your Mac and see if your time sync is off? Something seems to be an issue, and i don't think it's the server. At least, it shouldn't be missing more than before.
Sorry for the delayed reply. I was waiting to see if I hit this issue again. It seems like I hit it a few times right after upgrading but haven't hit it since (and in a month on the previous version I would have hit it more than once, so it seems like its doing better). The machine's time should be pretty close, its set against a GPS-synced NTP server on the LAN.
Hmm, yea, so its definitely better than it was, but I did run into it again this morning. Similar results, the stdout of the server process just shows nothing for the missing messages. Got a series of messages immediately in a row from someone, the first few got delivered (with corresponding New Message from... log output), then the remaining ones got nothing.