You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2021-09-28] If you mark a message as unread and close the app or minimize it, the unread status is removed. #4855
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
* Records the max action on app visibility change event.
*/
onVisibilityChange(){
if(Visibility.isVisible()){
updateLastReadActionID(this.props.reportID);
}
}
So, when we mark something as unread and change the app or try to close it, AppState's change event gets triggered, our handler gets triggered, since isVisible is always true, we end up marking the report as read, and hence, we don't get the marker again.
Proposal
Use AppState to get currentState and only return true when the app is active.
changed the title [-]If you mark a message as unread and close the app or minimize it, the unread status is removed.[/-][+][HOLD for payment 2021-09-28] If you mark a message as unread and close the app or minimize it, the unread status is removed.[/+]on Sep 21, 2021
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.0-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
OSBotify commentedon Aug 26, 2021
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
StagingDeployCashdeploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:MelvinBot commentedon Aug 26, 2021
Triggered auto assignment to @Jag96 (
Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.isagoico commentedon Aug 26, 2021
Confirmed this is also happening in Prod, removing the deploy blocker label.
MelvinBot commentedon Aug 26, 2021
Triggered auto assignment to @michaelhaxhiu (
External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.meetmangukiya commentedon Aug 27, 2021
This is not just for force close, this occurs for all activeReports. Whenever, the app visibility changes, the activeReport gets marked as read.
https://reactnative.dev/docs/appstate
Our
isVisibleimplementation for mobile always returns trueApp/src/libs/Visibility/index.native.js
Lines 1 to 7 in ae6a754
which leads to always marking the report as read irrespective of visibility changing to active or background
App/src/pages/home/report/ReportActionsView.js
Lines 241 to 248 in 8a5cf2d
So, when we mark something as unread and change the app or try to close it,
AppState'schangeevent gets triggered, our handler gets triggered, sinceisVisibleis always true, we end up marking the report as read, and hence, we don't get the marker again.Proposal
Use
AppStateto get currentState and only return true when the app is active.and change
onVisibilityChangemethod to check if app is active and drawer is not open34 remaining items
isagoico commentedon Sep 13, 2021
Issue reproducible during KI retests.
michaelhaxhiu commentedon Sep 15, 2021
Issue is still in progress, PR is seeing steady progress. Let's keep it up.
Jag96 commentedon Sep 15, 2021
PR merged!
botify commentedon Sep 15, 2021
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.
isagoico commentedon Sep 20, 2021
Issue reproducible during KI retests.
[-]If you mark a message as unread and close the app or minimize it, the unread status is removed.[/-][+][HOLD for payment 2021-09-28] If you mark a message as unread and close the app or minimize it, the unread status is removed.[/+]botify commentedon Sep 21, 2021
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.1.0-2 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2021-09-28. 🎊
isagoico commentedon Sep 27, 2021
Issue not reproducible during KI retests. (Fixed)
isagoico commentedon Oct 4, 2021
Issue not reproducible during KI retests. (Fixed)
Jag96 commentedon Oct 4, 2021
Paid!