Christoph Pader
Christoph Pader
I think we can close this issue, since there is a working solution! Let me know if this is not solved, then i'm gonna re-open :)
I've just posted a P/S thread for this here: https://expensify.slack.com/archives/C01GTK53T8Q/p1733938583809829
> @chrispader Do you have any ETA for moving this issue ahead? Do you need to hand over some of the other tasks to someone else in Margelo maybe? I'm...
@Christinadobrzyn @mountiny i added a WIP list of components and screens to migrate to the issue description. I'm actively working on adding all the components and screens, that we should...
# Approach / Proposal Triage all screens and components that contain modals into strictly necessary, beneficial and potential but not necessary issues. Once we've triaged all modals in screens and...
I've now updated the list of modals to the extent, that it includes all modals used in the app (that i could find through "smart" file search in VS Code...
I've just finished triaging all the modals in the codebase. (Hopefully i found all 😅) For each of the modals, you can find a detailed list of all the screens...
> @chrispader Would this work the same using `InteractionManager.runAfterInteractions` instead of `setTimeout` ? I'd go for that if it works the same, in order to avoid the other timeout variant....
@mountiny i created a tracking issue for a more holistic solution to this here: https://github.com/Expensify/App/issues/53493
> @chrispader Can you please add this to the issue to migrate to react-navigation modal so we do not forget to remove this once we migrate over? yes, will do!