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
[$500] iOS - Send message - "You appear to be offline.'' message is shown twice in IOS in New Chat Page #28326
changed the title [-]iOS - Send message - "You appear to be offline.'' message is shown twice in IOS in New Chat Page[/-][+][$500] iOS - Send message - "You appear to be offline.'' message is shown twice in IOS in New Chat Page[/+]on Sep 27, 2023
Please re-state the problem that we are trying to solve in this issue.
When offline, “You appear to be offline.'' message is shown twice in IOS in New Chat Selector Page. Only once it must be shown.
What is the root cause of that problem?
As shown here in the NewChatSelectorPage, the new chat selector page can either show NewChatPage or a tab with NewChatPage or WorkspaceNewRoomPage. Since NewChatPage and WorkspaceNewRoomPage are both showing Offline Indicator within their ScreenWrapper, the ScreenWrapper within NewChatSelectorPage will also duplicate the display of Offline Indicator. This is the root cause.
What changes do you think we should make in order to solve the problem?
To solve this problem, we can disable Offline Indicator for NewChatSelectorPage by setting shouldShowOfflineIndicator property to false in ScreenWrapperhere as follows:
Have confirmed can't reproduce on iphone and @kbecciv also confirmed in the thread, closing!
@zanyrenney@kbecciv
Can you please reconfirm reproducing this bug?
The reason for my request is that I am still able to reproduce this bug.
Please refer to the attached video that reproduces this issue for me.
Maybe we can reopen and fix this for $125 as it's super minor?
I can understand price being reduced initially itself. Or I can even understand price being reduced before receiving any proposals.
As I understand, sometimes the fix is simple and sometimes it takes much more time. So, overall, it get’s balanced. But, this does not mean that we can ignore the time spent to investigate.
To me, defining an issue super minor after receiving proposals does not sound fair.
Do we have any parallel to substantiate the previous comment?
Maybe, I am missing something here.
Yes. Agree that it is complex. But, I doubt if we can draw a parallel with that issue.
I have had experiences where the issue was closed by stating it as a non-issue even after I sent proposals. But, then, I can understand.
Anyway, to me, this issue happens in a typical flow of starting a new chat. And, I think, we cannot ignore it.
Looks like the confusion is in connection with reproducing this issue.
Activity
[-]iOS - Send message - "You appear to be offline.'' message is shown twice in IOS in New Chat Page[/-][+][$500] iOS - Send message - "You appear to be offline.'' message is shown twice in IOS in New Chat Page[/+]melvin-bot commentedon Sep 27, 2023
Job added to Upwork: https://www.upwork.com/jobs/~01bfe5272e5528fa4d
melvin-bot commentedon Sep 27, 2023
Triggered auto assignment to @zanyrenney (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Sep 27, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)melvin-bot commentedon Sep 27, 2023
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (
External)izarutskaya commentedon Sep 27, 2023
Proposal from @rayane-djouah
Please re-state the problem that we are trying to solve in this issue.
''You appear to be offline.'' message is shown twice in New Chat Page
What is the root cause of that problem?
the ScreenWrapper in NewChatPage component is showing a second offline message in addition to the existing one of the high level component.
What changes do you think we should make in order to solve the problem?
we should add
shouldShowOfflineIndicator={false}for the ScreenWrapper in NewChatPageApp/src/pages/NewChatPage.js
Lines 171 to 177 in cfad43f
Result:
https://github.com/Expensify/App/assets/77965000/adae6aa1-1cad-4546-a197-d07dd119d2d8
What alternative solutions did you explore? (Optional)
rojiphil commentedon Sep 27, 2023
Proposal
Please re-state the problem that we are trying to solve in this issue.
When offline, “You appear to be offline.'' message is shown twice in IOS in New Chat Selector Page. Only once it must be shown.
What is the root cause of that problem?
As shown here in the
NewChatSelectorPage, the new chat selector page can either showNewChatPageor atabwithNewChatPageorWorkspaceNewRoomPage. SinceNewChatPageandWorkspaceNewRoomPageare both showing Offline Indicator within theirScreenWrapper, theScreenWrapperwithinNewChatSelectorPagewill also duplicate the display of Offline Indicator. This is the root cause.What changes do you think we should make in order to solve the problem?
To solve this problem, we can disable Offline Indicator for
NewChatSelectorPageby settingshouldShowOfflineIndicatorproperty tofalseinScreenWrapperhere as follows:This will ensure that the duplicate Offline Indicator is not shown for both
NewChatPageandWorkspaceNewRoomPage.What alternative solutions did you explore? (Optional)
rayane-d commentedon Sep 27, 2023
Updated Proposal
original proposal link
Please re-state the problem that we are trying to solve in this issue.
''You appear to be offline.'' message is shown twice in New Chat Page and New Room Page
What is the root cause of that problem?
the ScreenWrapper in NewChatPage component and the ScreenWrapper in WorkspaceNewRoomPage are showing a second offline message in addition to the existing one in the ScreenWrapper of the higher order component NewChatSelectorPage.
What changes do you think we should make in order to solve the problem?
we should set
shouldShowOfflineIndicatorproperty tofalsein the the ScreenWrapper in NewChatPage component and the ScreenWrapper in WorkspaceNewRoomPageWhat alternative solutions did you explore? (Optional)
13 remaining items
melvin-bot commentedon Oct 11, 2023
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸
zanyrenney commentedon Oct 12, 2023
bump @rushatgabhane can you review the proposal?
melvin-bot commentedon Oct 16, 2023
@rushatgabhane, @zanyrenney Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
zanyrenney commentedon Oct 16, 2023
Have confirmed can't reproduce on iphone and @kbecciv also confirmed in the thread, closing!
rojiphil commentedon Oct 16, 2023
@zanyrenney @kbecciv
Can you please reconfirm reproducing this bug?
The reason for my request is that I am still able to reproduce this bug.
Please refer to the attached video that reproduces this issue for me.
28326-issue.mp4
rojiphil commentedon Oct 27, 2023
@zanyrenney
I fail to understand why this issue is closed as I can still reproduce this in v 1.3.91-6
Anything I am missing here?
Here is a test video that reproduces the problem:
28326-reproduced.mp4
situchan commentedon Oct 27, 2023
@zanyrenney this is still reproducible. Maybe we can reopen and fix this for $125 as it's super minor?
rojiphil commentedon Oct 27, 2023
I can understand price being reduced initially itself. Or I can even understand price being reduced before receiving any proposals.
As I understand, sometimes the fix is simple and sometimes it takes much more time. So, overall, it get’s balanced. But, this does not mean that we can ignore the time spent to investigate.
To me, defining an issue super minor after receiving proposals does not sound fair.
Do we have any parallel to substantiate the previous comment?
Maybe, I am missing something here.
situchan commentedon Oct 27, 2023
Example: #29459 (comment), though it end up being complex
rojiphil commentedon Oct 27, 2023
Yes. Agree that it is complex. But, I doubt if we can draw a parallel with that issue.
I have had experiences where the issue was closed by stating it as a non-issue even after I sent proposals. But, then, I can understand.
Anyway, to me, this issue happens in a typical flow of starting a new chat. And, I think, we cannot ignore it.
Looks like the confusion is in connection with reproducing this issue.