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

[Bug] Email not marked as read when inside thread #242

Open
EvilVir opened this issue Jun 20, 2024 · 7 comments
Open

[Bug] Email not marked as read when inside thread #242

EvilVir opened this issue Jun 20, 2024 · 7 comments
Assignees
Labels
bug Something isn't working synchronization integrator synchronization issues

Comments

@EvilVir
Copy link

EvilVir commented Jun 20, 2024

Describe the bug
If I have email's thread and select one of the messages it gets marked as read but it doesn't save and badge on the sidebar doesn't disappear. Next time I reopen the mailbox same email is again marked as unread.

Expected behavior
Emails should be properly marked as read.

Screenshots
image

Additional context
Outlook.com mailbox, Wino 1.7.3 from Windows Store

@EvilVir EvilVir added the bug Something isn't working label Jun 20, 2024
@Tiktack
Copy link
Contributor

Tiktack commented Jun 20, 2024

Cannot re-produce, just tested 5 different threads. It works. I can admit there is some delay before bage updates, but it works.
Gmail account, 1.7.3 version.

@EvilVir
Copy link
Author

EvilVir commented Jun 20, 2024

I need to go out now but later I will record a video of this happening and send to you.

Have you checked exactly on Outlook.com mailbox? I feel like connector for Outlook is, in general, buggy compared to Gmail one.

@EvilVir
Copy link
Author

EvilVir commented Jun 20, 2024

@bkaankose
Copy link
Owner

I agree that Outlook synchronizer is more buggy compared to Gmail one. Gmail has better API exposure, much easier to deal with to be honest...

Wino sends the request for marking the mail as read, applies a UI change (that's why you see it's marked as read in the mailing list), then triggers a quick synchronization to sync changes to acknowledge whether API responded to your 'mark as read' change. Badge is updated after this sync is done and your mail is marked as 'read' in the local database.

Probably something went wrong with the API call, and it's not reported back to Wino. It might be logged though. In the current version sharing logs is buggy, but it'll be fixed for the next release.

Could you manually share WinoDiagnostics.log file under this location:

C:\Users\YourUserName\AppData\Local\Packages\58272BurakKSE.WinoMailPreview_mhdqskaa8n2sj\LocalState

Don't forget to change the YourUserName part with your username. You can also delete this file (when the app is not running) and re-launch the app to have clear logs of this issue. I can investigate the issue based on this log.

@EvilVir
Copy link
Author

EvilVir commented Jun 20, 2024

WinoDiagnostics.log

Here you go :)

@Basti-3
Copy link

Basti-3 commented Jun 21, 2024

I, too, noticed this issue. Wanted to file a report just now after encountering it a second time.
I had a normal E-Mail. Outlook.com and the mobile Outlook App reported the E-Mail as already being read, while Wino showed it as unread and wouldn't budge.
The fix was to mark it as unread on Outlook.com and then close and reopen Wino. Then click on the E-Mail, after which it correctly marked the E-Mail as read and synchronised everything correctly.

@bkaankose bkaankose added the synchronization integrator synchronization issues label Jun 21, 2024
@bkaankose
Copy link
Owner

Looks like somehow marking that mail as read is missed during synchronization, but the folder's last sync identifier is updated to latest token. Unfortunately I couldn't detect anything from the logs.

I would try to replicate with different scenarios to see if I can reproduce it on my end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working synchronization integrator synchronization issues
Projects
None yet
Development

No branches or pull requests

4 participants