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
Version Number: 1.4.44 Reproducible in staging?: Y Reproducible in production?: N 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:
Launch app
Tap fab-assign task
Enter title and tap next
Select share somewhere
Tap Create task
Tap on new task created to open details page
Tap assignee
Or
Tap settings
Tap workspaces----workspace
Tap members
Tap invite members
Expected Result:
In task details page, tapping assignee must show contacts page
Tapping Workspace invite members must display contacts and must not load infinitely.
Actual Result:
In task details page, tapping assignee shows infinite loading page.
Tapping Workspace invite members is also loading infinitely.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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.
Please re-state the problem that we are trying to solve in this issue.
In task details page, tapping assignee shows infinite loading page.
What is the root cause of that problem?
The didScreenTransitionEndhere on Android is always false, that's because the event here never fires. This transitionEnd has been known to be unreliable, which is why we ditched this approach and used this approach instead to be sure the transition has ended (it has been used in several places as part of the useAutoFocusInput hook)
What changes do you think we should make in order to solve the problem?
Extract this logic to a useIsScreenTransitionEnded hook, which will return a isScreenTransitionEnded boolean value indicating if the screen transition has ended
Use that hook in here and in places that use didScreenTransitionEnd in there, use the boolean returned from the hook instead.
What alternative solutions did you explore? (Optional)
We can use the useIsScreenTransitionEnded hook inside the ScreenWrapper itself and pass it down to child components, and not relying on the navigation event any more.
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.45-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon Feb 27, 2024
Unable to auto-create job on Upwork. The BZ team member should create it manually for this issue.
melvin-bot commentedon Feb 27, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (
External)github-actions commentedon Feb 27, 2024
👋 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:
melvin-bot commentedon Feb 27, 2024
Auto-assign attempt failed, all eligible assignees are OOO.
lanitochka17 commentedon Feb 27, 2024
We think that this bug might be related to #vip-vsp
CC @quinthar
dukenv0307 commentedon Feb 27, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
In task details page, tapping assignee shows infinite loading page.
What is the root cause of that problem?
The
didScreenTransitionEndhere on Android is always false, that's because the event here never fires. ThistransitionEndhas been known to be unreliable, which is why we ditched this approach and used this approach instead to be sure the transition has ended (it has been used in several places as part of theuseAutoFocusInputhook)What changes do you think we should make in order to solve the problem?
We should use this agreed approach to detect transition end in this case too.
We can do that by:
useIsScreenTransitionEndedhook, which will return aisScreenTransitionEndedboolean value indicating if the screen transition has endeddidScreenTransitionEndin there, use the boolean returned from the hook instead.What alternative solutions did you explore? (Optional)
We can use the
useIsScreenTransitionEndedhook inside theScreenWrapperitself and pass it down to child components, and not relying on the navigation event any more.s77rt commentedon Feb 27, 2024
A regression from #29991.
@hannojg @kirillzyusko This is another case of #37156
7 remaining items
[-]Android - Task-Tapping assignee shows infinite loading page[/-][+][HOLD for payment 2024-03-07] Android - Task-Tapping assignee shows infinite loading page[/+]melvin-bot commentedon Feb 29, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 29, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.45-6 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 2024-03-07. 🎊
For reference, here are some details about the assignees on this issue: