-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2023-12-13] [$1000] Deeplink - FAB menu briefly shown when navigate to concierge deeplink with new account #30021
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01277cf9c667bd137d |
Triggered auto assignment to @kadiealexander ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @jjcoffee ( |
@abzokhattab The FAB is displaying open in your screenshot, which it shouldn't be. |
ProposalPlease re-state the problem that we are trying to solve in this issue.FAB menu shown when navigate to concierge deeplink with new account What is the root cause of that problem?this Happens because we are explictly opening Popover when the route name is "home" or "CentralPaneNavigator". we are not returning early incase of full width report view (mobile screen width), hence the popover menu opens
because of this useEffect when navigation to conceirge trigerred the screen becomes inactive and popover hides, but this isn't the case for ios native there must a race condition in screen getting focussed and fab menu becoming visible because fab option stays open ios native and don't hide when chat is open.
Fab Menu auto. opens for new users only, as a new user there is no chat a user a can deeplink to so this doesn't happen for other chats but for concierge only. What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)N/a |
My main proposal is so that the FAB will reopen to onboard users after coming back from Concierge, while the alternate proposal is in case we decide the FAB should not open. ProposalPlease re-state the problem that we are trying to solve in this issue.The FAB menu is briefly displayed when navigating to the concierge chat. The FAB icon is displayed as "x" instead of "+" What is the root cause of that problem?We're allowing the Create menu to open here as long as the currentRoute is either The Create menu opens briefly because in here, we have the logic to hide the create menu if the screen is unfocused. So the Create menu only shows for a bit, then is closed. Sometimes we'll see that the Create menu opens and stay there (it does disappear), because there's a race condition here, where the screen unfocusing and the This is only happening for small screen because in large screen, the LHN along with the floating button will show side-by-side with the opened report, so it makes sense for the FAB menu to show upon concierge deeplink navigation. Meanwhile for small screen, the floating button and opened report are on 2 different screens so it Concierge shows, the FAB menu should not show. What changes do you think we should make in order to solve the problem?On small screen width device, we should show the Create menu only if the SidebarScreen is having focus. We can update this to
We can consider setting the state of the FAB button based on the same condition as well, although if the screen is not focused, we won't be seeing the FAB button anyway. Although not strictly required for this issue, if we want to fix the race condition mentioned in the RCA, we can move this line to before this one so we'll always set What alternative solutions did you explore? (Optional)If we don't want to reopen the FAB after going back from Concierge, we can make sure we use a |
@jjcoffee, @kadiealexander Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@jjcoffee any thoughts on the proposals above? |
Neither of the proposals explain why the FAB only shows briefly. Also why is this only happening for the concierge chat (if that's actually the case)? |
because of this useEffect when naivgation to conceirge trigerred the screen becomes inactive and popover hides, but this isn't the case for ios native there must a race condition in screen getting focussed and fab menu becoming visible because fab option stays open ios native and don't hide when chat is open.
Fab Menu auto. opens for new users only, as a new user there is no chats a user a can deeplink to so this doesn't happen for other chats but for concierfe only. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Upwork job price has been updated to $1000 |
Not overdue, get your proposals in! |
I'll provide a detailed update shortly on this |
Haha well, looks like we're still on a 50:50 split on Slack about this, but I think we can just go ahead with @dukenv0307's proposal here. The RCA is correct and sufficiently detailed, and the solution is nice and straight forward. In comparison @rojiphil's proposal feels a bit over-engineered when we can have a much simpler fix. 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @lakchote, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@lakchote We were trying to settle on the right behaviour once we navigate back from the concierge chat, i.e. should the create menu show as open, or does it make sense to keep it hidden since we've already navigated directly to a chat. I asked on Slack but we're pretty much at a 50:50 split 😄 Let me know if you have any thoughts, otherwise I think we can just go with what @dukenv0307 has in their proposal (open once navigating back from the chat). |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@jjcoffee In my opinion, we shoud show the FAB but only once? It's important to clearly communicate the value of the app, and I think by showing it once to the user is a good idea to convert them to paid down the line. If we did it more than once, it could be frustrating. @dukenv0307's proposal LGTM 👍 |
📣 @jjcoffee 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @dukenv0307 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@jjcoffee The PR is ready for review. |
Issue not reproducible during KI retests. (First week) |
Deployed to production Dec 6, not sure what happened to the automation! @kadiealexander Can you update the title and add the |
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Regression Test Proposal For small screen devices only:
Do we agree 👍 or 👎 |
Issue is ready for payment but no BZ is assigned. @stephanieelliott you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Everyone is paid! |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.3.87-1
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
Concierge chat is opened, and the FAB menu is not displayed
Actual Result:
The FAB menu is briefly displayed when navigating to the concierge chat. The FAB icon is displayed as "x" instead of "+"
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Bug6243487_1697744044675.video_2023-10-19_15-29-54.mp4
0-02-01-a546fbcbcd25efb0d31ad3d4733437f49ef76d416931d3aded2e1ec08630f9a5_c0f77a4a57c59d14.1.mp4
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @lakchoteThe text was updated successfully, but these errors were encountered: