[New architecture] Popover modals are not visible when opened

[j-piasecki]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

This issue is related to the ongoing new architecture adoption. It was reported on the build with new architecture enabled on the relevant PR.

---

Version Number: 1.4.42-1
Reproducible in staging?: no
Reproducible in production?: no
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: @ishpaul777 here and here
Slack conversation:

Action Performed:

Open a popover modal

• by clicking the FAB on the LHN
• by clicking the ➕ icon in the composer
• by pressing the photo icon in the Add receipt screen

Expected Result:

The popover modal should appear

Actual Result:

The backdrop is visible but the popover itself is not.

Workaround:

Unknown, should be fixed by 6816b93

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence


popover2.mov

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~013d3bfa0df549c01f
• Upwork Job ID: 1768714498647588864
• Last Price Increase: 2024-03-15

[melvin-bot]

Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[melvin-bot]

Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

Huh... This is 4 days overdue. Who can take care of this?

[ishpaul777]

Not able to repro with latest build 👍

[melvin-bot]

6 days overdue. This is scarier than being forced to listen to Vogon poetry!

[MitchExpensify]

Just to be sure before I close, what "popover" are you referring to in the issue @ishpaul777 ?

[melvin-bot]

Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

[MitchExpensify]

Just to be sure before I close, what "popover" are you referring to in the issue @ishpaul777 ?

bump @ishpaul777

[ishpaul777]

Sorry i missed the ping earlier, the issue was found while testing #13767 and created for tracking purpose, now its fixed in PR but we decide to keep it open so this can be tested again by QA team on staging once Pr is merged

[melvin-bot]

Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

Whoops! This issue is 2 days overdue. Let's get this updated quick!

[MitchExpensify]

Waiting on this PR to hit staging to test again

[melvin-bot]

this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

[MitchExpensify]

PR hasn't hit staging yet to retest

[melvin-bot]

Whoops! This issue is 2 days overdue. Let's get this updated quick!

[tgolen]

This issue is unassigned. Who is working on this and taking responsibility for it? @ishpaul777 would that be you or would it be @MitchExpensify ?

[ishpaul777]

This issue was found while testing PR #13767 and is resolved in the PR #13767 but we have kept it open so QA will retest when PR hits staging. Any bugs with [New architecture] that are unassigned are probably only for tracking purpose.

[melvin-bot]

this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!

[tgolen]

Hm, but we don't keep around unassigned issues just for tracking purposes. If the problem has been fixed, and nothing is left to do, then I'm just going to close it. Thanks!