Message Status is Incorrect When Receiving All Messages From the Server #59

Closed
opened 2020-09-27 14:18:26 +02:00 by mpk · 3 comments
Owner

How to reproduce:

  • Clear/Delete your local database
  • Start envoy
    -> all Messages that should be READ have the status RECEIVED (Not tested with messages that should not have status READ.

The server sends the messages with the wrong status.

How to reproduce: * Clear/Delete your local database * Start envoy -> all Messages that should be READ have the status RECEIVED (Not tested with messages that should not have status READ. The server sends the messages with the wrong status.
mpk added this to the v0.2-beta milestone 2020-09-27 14:18:26 +02:00
mpk added the
bug
M
server
labels 2020-09-27 14:18:27 +02:00
mpk changed title from Mesage Status is Incorrect When Receiving All Messages From the Server to Message Status is Incorrect When Receiving All Messages From the Server 2020-09-27 14:19:52 +02:00
mpk closed this issue 2020-09-27 15:56:00 +02:00
mpk reopened this issue 2020-09-27 16:06:23 +02:00
mpk modified the milestone from v0.2-beta to v0.3-beta 2020-09-27 17:01:32 +02:00
Owner

Incorrect. I followed your given step to the letter, and this was the result returned:
image
as you can see, these messages are still read, as they should be.

Could you maybe clarify when exactly this happened and how?
Another question: You claim, the server sent those messages wrong. Did you validate it with postgres/ the database view in Eclipse?

Incorrect. I followed your given step to the letter, and this was the result returned: ![image](/attachments/ecfb79dc-9c98-4481-8526-497b6f36ac61) as you can see, these messages are still read, as they should be. Could you maybe clarify when exactly this happened and how? Another question: You claim, the server sent those messages wrong. Did you validate it with postgres/ the database view in Eclipse?
Owner

Still incorrect.
I followed your instructions with group chats and still got the same result:
image

Please provide a better reproduction mechanism

Still incorrect. I followed your instructions with group chats and still got the same result: ![image](/attachments/e8189c92-8e61-4df0-9e9d-913c830ebc8f) Please provide a better reproduction mechanism
Owner

As this issue is currently not reproducible, I'll assign it a due date and if nothing has changed by then, it'll be closed

As this issue is currently not reproducible, I'll assign it a due date and if nothing has changed by then, it'll be closed
delvh added the due date 2020-10-11 2020-10-04 10:03:47 +02:00
kske closed this issue 2020-10-13 07:47:52 +02:00
This repo is archived. You cannot comment on issues.
No description provided.