-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[C+ Checklist Needs Completion] [$1000] DEV:Takes time to change topbar(manual to scan, scan to manual) selection in request money #25428
Comments
Triggered auto assignment to @greg-schroeder ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Tab change not animating when screen is swiped when on MoneyRequestPage. What is the root cause of that problem?The root cause is that we're having static values as background colours for the buttons, icons and text inside the tab. What changes do you think we should make in order to solve the problem?We need to make use of the position property here and pass that onto the
These interpolated values of colours are then to be used inside What alternative solutions did you explore? (Optional)We can also just disable the swipe on web so that the user can only switch the tab by pressing the button itself. However, I think that the solution proposed above is more elegant. |
Job added to Upwork: https://www.upwork.com/jobs/~010c514d8b4722d88a |
Current assignee @greg-schroeder is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @burczu ( |
I can't repro DEV issues - I'm assuming since you made a proposal here @allroundexperts that you were able to? |
Hi @greg-schroeder! Yes, this is easily reproducible. @shawnborton How should the animation look like here? Do you think animating the colours as the user slides the screen makes sense? |
ProposalPlease re-state the problem that we are trying to solve in this issue.Tab change animations are delayed when the screen is swiped when on MoneyRequestPage. What is the root cause of that problem?The root cause of this problem is that by default, React Navigation lazy loads tab screens, which means that the screens are only rendered when accessed for the first time. This can cause a delay in rendering the new tab screen when swiping. When the screen is swiped, the new tab screen needs to be rendered immediately to provide a smooth transition. However, because of lazy loading, there is a delay in rendering the new tab screen, resulting in delayed animation. What changes do you think we should make to solve the problem?What we need to do is simply disable lazy by setting the
What alternative solutions did you explore? (Optional)None |
This is not a bug, we can close. cc @AndrewGable |
@shawnborton Is there any specific reason why this is not a bug? The tabs are clearly getting stuck. |
Based on the video the tabs don't look stuck. Looks like they slide in and out as intended. |
@shawnborton Please watch from 8s onwards. |
It's really hard to tell because the mouse is moving like crazy in that video. Can we create a new video where the mouse is doing normal gestures? |
Here you go @shawnborton. Screen.Recording.2023-08-18.at.6.12.19.PM.mov |
Cool, thanks for that. Curious for @AndrewGable's thoughts here. |
ProposalSelection change between tab screens is not immediate due to not using realtime animation of tab active state. Please re-state the problem that we are trying to solve in this issue.Make tabs active state have a faster feedback between screen changes. What is the root cause of that problem?It takes about a second for What changes do you think we should make in order to solve the problem?Instead of changing states based on tabs_active_state.movWhat alternative solutions did you explore? (Optional)I consider adding new animations a risk at the moment. There is an android crash in react native related to animations. If it is not urgent, this should wait for that bug to be fixed in react native first, otherwise fixing this could introduce a different bug. |
going to wait on @AndrewGable's take before I take any action on this one like potentially closing or not |
bump @AndrewGable |
Yes this is something that can be improved. I agree with it being a bug. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.60-3 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 2023-09-07. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.61-3 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 2023-09-08. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
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:
|
Processing payments |
Was this issue merged in time to be eligible for the speed bonus? ❌ Payment summary: Reporter: @niravkakadiya25 - $250 |
Offer sent to @niravkakadiya25. @allroundexperts you can make a manual request. All that's left is the checklist. |
Requested. |
$1,000 payment approved via NewDot based on BZ summary. |
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:
|
@burczu @greg-schroeder @allroundexperts @thienlnam this issue is now 4 weeks old and preventing us from maintaining WAQ, can you:
Thanks! |
Current assignees @burczu and @allroundexperts are eligible for the Internal assigner, not assigning anyone new. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
selection change should be immediately
Actual Result:
selection change takes some time
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: Dev
Reproducible in staging?: dev
Reproducible in production?: dev
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
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2023-08-16.at.5.42.59.PM.mov
Expensify/Expensify Issue URL:
Issue reported by: @niravkakadiya25
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1691384151135339
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: