Expose chat read positions and E2EE errors

Add optional chat activity and read-position details to the unread-count endpoint. Return stable E2EE rejection codes for stale timestamps and untrusted signing devices, with tests for both behaviors.
This commit is contained in:
Artemy
2026-11-15 21:26:00 +07:00
parent def724e0ee
commit 31d704712c
9 changed files with 108 additions and 8 deletions
+9
View File
@@ -101,7 +101,16 @@ public class ChatsHub : Hub
var result = await _messageSendingService.SendMessageAsync(sendParams);
if (!result.IsSuccess)
{
if (result.Exception is UnauthorizedAccessException { Message: E2eeProtocol.SigningDeviceRejectedError })
{
_logger.LogWarning("Message rejected for {UserId}: {Reason}", userId, E2eeProtocol.SigningDeviceRejectedError);
return HubResult<UserMessageResponse>.Forbidden(E2eeProtocol.SigningDeviceRejectedError);
}
if (result.Exception is ArgumentException { Message: E2eeProtocol.TimestampOutOfRangeError or E2eeProtocol.DevicesChangedError } rejection)
_logger.LogWarning("Message rejected for {UserId}: {Reason}", userId, rejection.Message);
throw result.Exception ?? new InvalidOperationException("Failed to send message");
}
var response = MapToResponse(result.Message, request.ReplyToMessageId);