Update portal.go for macOS Tahoe #231
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix for "any" type rooms on macOS Tahoe
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix delivery receipts on macOS Tahoe (26)
Problem
macOS Tahoe (26) changed the chat GUID format in the Messages database. Previously, DM chat GUIDs were formatted as:
Tahoe now uses:
The
service_namecolumn still correctly containsiMessage, but the GUID prefix changed toany.This caused the delivery status check on line 1129 to fail for iMessage DMs, resulting in Beeper/Matrix clients showing "Sent" instead of "Delivered".
Fix
Accept
"any"as a valid service type for iMessage DMs when determining whether to send delivery status events.Tested with