Franz: Messages not getting automatically marked as read in slack

Created on 21 Jun 2019  ·  10Comments  ·  Source: meetfranz/franz

Describe the bug
Messages in slack are not automatically marked as read when clicking on a channel or private message.

You can click the "x" at the top to mark them as read but up until just recently that wasn't necessary.

My slack settings are set to:
"When I view a channel: Start me where I left off and mark the channel as read"

To Reproduce
Steps to reproduce the behavior:

  1. Send a message from one user to another or to a channel
  2. In franz you'll see that despite you've viewed the private message or channel the unread notification in slack doesn't go away.
  3. To dismiss it you have to click the x at the top which says:
    %x% new message since %time% on %date% x

Expected behavior
Viewing a private message or channel should mark that channel or private message as read.

Screenshots
If applicable, add screenshots to help explain your problem.
2019-06-20_19h26_16

Desktop (please complete the following information):

  • OS: Windows 2019
  • Browser ? I have Opera, Chrome, Firefox installed but I'm not sure that's relevant to this issue
  • Version [e.g. 22] Not sure that is relevant to this issue.

Smartphone (please complete the following information):
N/A

Additional context
Add any other context about the problem here.

Most helpful comment

Looks like Franz released 5.0.0-beta.3 which at least for me fixes the issue.

All 10 comments

I've the same issue.

+1
Not sure if is related but some times I cannot paste (ctrl+v) an image in a message.

Since the last update (5.2.0-beta.2) it seems to me that keyboard shortcuts like ctr+v or ctrl+k stop working after a certain time after Franz was started

Same problem with both messages not being marked as read and the ctrl+v
paste issues.
-

On Tue, Jun 25, 2019 at 9:36 AM Holger Banse notifications@github.com
wrote:

Since the last update (5.2.0-beta.2) it seems to me that keyboard
shortcuts like ctr+v or ctrl+k stop working after a certain time after
Franz was started


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/meetfranz/franz/issues/1496?email_source=notifications&email_token=AAPTY77KKFTFMSSCCA23GKLP4G4IJA5CNFSM4H2DADPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPF55I#issuecomment-505306869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPTY73RQHY6FQM73LSNEK3P4G4IJANCNFSM4H2DADPA
.

Same here, I use the same version 5.0.0-beta.2 both in Windows and Mac and this issue only happens in Windows.

Looks like Franz released 5.0.0-beta.3 which at least for me fixes the issue.

Looks like this issue is back (Version 4.4.1, macOS Mojave, Version 20.03.20, iOS). Thread replies not marking themselves as read, and notification remaining in app icon in the dock, and showing "1 new reply" notification in both. Annoying AF.

Yes, the issue is definitely back. I've never had a problem with things not marking read, but now I can be in a channel, a direct message, or a thread and see it. Esc doesn't usually work; Shift-Esc doesn't seem to work, either. For the most part, I don't know if anybody has pinged me, because the tray icon shows red all the time.

Windows 10 Pro 1909
Production 4.4.0 64-bit

Same problem. Messages not marked as read. Windows 10.

Happens to me also quite often. Using the "mark as read" from the channel's context menu works however.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

m2kk picture m2kk  ·  4Comments

larissaales picture larissaales  ·  3Comments

sach160 picture sach160  ·  4Comments

thmsnhl picture thmsnhl  ·  4Comments

kingjr picture kingjr  ·  3Comments