Status-react: New messages counter is shown for already seen messages

Created on 8 May 2018  ·  35Comments  ·  Source: status-im/status-react

User Story

As a user I don't want to see new messages counter when all messages are already seen

Description

Type: Bug

Summary: New messages counter doesn't disappear until navigating to home view if a new message was received when viewing another user profile or group chat info. Even if a user already read all new messages and sent new one on the chat the counter is still present

Expected behavior

New messages counter disappears when a user navigates to a chat with new messages

Actual behavior

New messages counter is still shown when user returns to a chat with new messages from profile or group info view

Reproduction

One-to-one chat:

  • Open Status on 2 devices
  • Create 2 users and start a chat between them
  • As user A tap Chat options -> View profile
  • As user B send a message to user A
  • As user A return to the chat view and send a message to user B

Group chat:

  • Open Status on 2 devices
  • Create 2 users
  • Create a group chat
  • As user A click Chat options -> Group info
  • As user B send a message in the group chat
  • As user A return to the chat view and send a message in the group chat

Public chat:

  • Open Status on 2 devices
  • Create 2 users and join the same public chat
  • As user B send a message in the public chat
  • As user A tap user's B picture and open his profile
  • As user B send one more message in the chat
  • As user A return to the chat view and send a message

Additional Information

  • Status version: 6fc03fc2, nightly build from May 8
  • Operating System: Android, iOS
bounty bounty-s bug chat chat-reliability low-severity

All 35 comments

The issue is still present in 0.9.20 build. But, it does not seem to be related to #4820 in which the message counter does not disappear even if the chat is opened again.

@lukaszfryc @yevh-berdnyk is this issue still relevant?

@andytudhope yes, it's still reproducible on both iOS and Android

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__This issue now has a funding of 120.0 DAI (120.0 USD @ $1.0/DAI) attached to it as part of the Status-im fund.__

@StatusSceptre can I work on this issue?

Feel free to open a pull request if you’re inclined to work on it! We’re happy to accept commits.

@mul1sh would be happy to have you dive into the fix, Status works with CLJS not JS would you be comfortable with it? If you feel confident to start work I can approve you no problem!

@StatusSceptre yes i'm very confident with CLJS so i can definitely handle this task. thanks 🙂

You've been approved to start work @mul1sh!

@StatusSceptre awesome thanks

@StatusSceptre sorry, but i'm having a bit of an issue deploying the app on my end. So let me stop the work for now so that i don't block this issue for long and then once I understand how to correctly deploy the app, I'll jump in future issues.

Sincere apologies for the inconvenience caused

@mul1sh we want to make sure you can build the app to successfully work, there is no rush on this issue. Have you tried following along with https://status.im/build_status/

Would love to see you continue work on this!

If you still have problems after following along there please drop a message here:

Check out this public chat on the Status app: https://get.status.im/chat/public/status-core

@StatusSceptre ohh nice, thanks. I didn't know the docs for the app were available and the way i wasted so much time trying to do it on my own 🤦‍♂️ Anyway thanks for sharing, let me try building the app as per the docs.

I can confirm issue still present with 0.9.33 Develop/Release builds.
Message counter (near the top-left < button on chat view) does not disappear when navigating to chat view from user Profile / Wallet modal / Group info(for Group chat) views

No problem @mul1sh just keep us updated on your work if you have a WIP or need any other assistance!

@mul1sh are you still working on this issue?

Issue Status: 1. Open 2. Cancelled


__The funding of 120.0 DAI (120.0 USD @ $1.0/DAI) attached to this issue has been cancelled by the bounty submitter__

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__This issue now has a funding of 230.0 DAI (230.0 USD @ $1.0/DAI) attached to it as part of the Status-im fund.__

@StatusSceptre @pablanopete yes I'm still working on this issue, sorry I forgot to reply.

I tried a number of fixes last week and I found one that finally sticks, was going to push it after i'm done testing, but i see the issue has been cancelled now 🙁 .

@mul1sh it's still active!

@StatusSceptre awesome will submit to it soon then :)

Commits > Comments ;)

@mul1sh says he's working on it but feel free to collaborate with him @leonardohof !

@mul1sh are you still working on this?

@StatusSceptre yes I am, sorry for the late reply. But I will PR in a few hours 🙂 thanks.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__Work has been started__.

These users each claimed they can complete the work by 10 months, 1 week from now.
Please review their action plans below:

1) bitsikka has started work.

I would as needed modify status-im.ui.screens.navigation/navigate-back which is used in all three cases. I will make use of status-im.chat.models/mark-messages-seen in it.

Learn more on the Gitcoin Issue Details page.

oops! didn't realize you were working on this @mul1sh. Are you still working on it?

I was browsing through issues in gitcoin and saw that this issue had "Ready to work" status, and that previous person @leonardohof had stopped working on it.

@bitsikka no worries, you can continue working on this because to be honest my PR is still in the works as I'm still learning the code. So go ahead and knock this one out 😃

@mul1sh thanks! I'm also still learning 😄 and this is going to be my first PR.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__Work for 230.0 DAI (230.0 USD @ $1.0/DAI) has been submitted by__:

  1. @bitsikka

@StatusSceptre please take a look at the submitted work:

  • PR by @bitsikka

@StatusSceptre looks like you have a PR submission from @bitsikka!

awaiting the merge.

@PombeirP is this work completed and ready for payout?

@StatusSceptre yes, respective PR with a fix has merged. Ready for payout.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


__The funding of 230.0 DAI (230.0 USD @ $1.0/DAI) attached to this issue has been approved & issued to @bitsikka.__

Was this page helpful?
0 / 5 - 0 ratings

Related issues

churik picture churik  ·  54Comments

jakubgs picture jakubgs  ·  54Comments

jeluard picture jeluard  ·  68Comments

rachelhamlin picture rachelhamlin  ·  49Comments

hesterbruikman picture hesterbruikman  ·  41Comments