# Topics incorrectly stuck in unread state on Android in Chrome 77
**URL:** https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907
**Category:** Bug
**Created:** [October 1, 2019, 2:37am UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907 "2019-10-01T02:37:03Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [October 1, 2019, 2:37am UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907/1 "2019-10-01T02:37:03Z")
Per: [Unread tab does not update after reading](https://meta.discourse.org/t/unread-tab-does-not-update-after-reading/129162)
There were quite a few people mentioning issues with topics not being marked read on Android.
We have done some root cause analysis and found that the page visibility api changed the way it operates in Android Chrome 77.
It was discussed in brief here:
[https://github.com/pgilad/react-page-visibility/issues/9](https://github.com/pgilad/react-page-visibility/issues/9)
There is a fancy graph that explains the new lifecycle here:
> **[Page Lifecycle API | Web Platform | Chrome for Developers](https://developer.chrome.com/docs/web-platform/page-lifecycle-api)**
>
> The Page Lifecycle API brings app lifecycle features common on mobile operating systems to the web. Browsers are now able to safely freeze and discard background pages to conserve resources, and developers can safely handle these interventions...
The symptoms of the issue is.
- You use your android
- You flip to do something else for 5-10 minutes
- You flip back to Discourse and nothing is marked read anymore
I made a fix for this here:
[https://github.com/discourse/discourse/commit/499472b6a0e9bd0cef4539287e9845476938cf01](https://github.com/discourse/discourse/commit/499472b6a0e9bd0cef4539287e9845476938cf01)
In “theory” it should resolve the issue.
cc @mcwumbly / @Heather_Dudley / @Yuun
This fix will be deployed on meta shortly, you will have to do a full reload to get it applied.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [October 1, 2019, 3:40am UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907/2 "2019-10-01T03:40:24Z")
Also applies to you @Wingtip
---
### Author:  [@Wingtip](https://meta.discourse.org/u/Wingtip)
#### Post date: [October 1, 2019, 12:12pm UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907/3 "2019-10-01T12:12:20Z")
Fantastic, is the fix available yet? On 2.4.0.beta4 [0420e8145e] now.
---
### Author:  [@pmusaraj](https://meta.discourse.org/u/pmusaraj)
#### Post date: [October 1, 2019, 1:26pm UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907/4 "2019-10-01T13:26:56Z")
Yes, the fix is included on `0420e8145e`.
---
### Author:  [@Wingtip](https://meta.discourse.org/u/Wingtip)
#### Post date: [October 1, 2019, 3:03pm UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907/5 "2019-10-01T15:03:09Z")
Looks to have worked! Thanks again.
---
### Author:  [@Heather\_Dudley](https://meta.discourse.org/u/Heather_Dudley)
#### Post date: [October 6, 2019, 7:08pm UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907/6 "2019-10-06T19:08:07Z")
Seems to be working for us now, too. I haven’t had this issue on meta anymore, and what unread issues we’re having on my installation are related to network traffic, not the bug.
Thank you guys!
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [October 6, 2019, 10:17pm UTC](https://meta.discourse.org/t/topics-incorrectly-stuck-in-unread-state-on-android-in-chrome-77/129907/7 "2019-10-06T22:17:15Z")