Eugene Voloshchak

> In mweb, when banner pop up remains opened, expensify logo and profile icon cannot be seen but in Android app, it can be seen @strepanier03, I'm not sure if...

Not overdue, waiting on proposals

> However, memory is more limited and valuable on mobile devices compared to disk space, which can lead to high memory usage, but it is very effective in avoiding loading...

- The PR that introduced the bug has been identified. Link to the PR: there isn't a PR that has caused this, this was caused by images taking too long...

Huh, that is an interesting issue Thanks for the bump, I did miss the one on the weekend! @khaterdev's proposal looks promising, but I'm not 100% sure just yet and...

@khaterdev, I think you're onto something,[proposal](https://github.com/Expensify/App/issues/19507#issuecomment-1574401451) is good, , but there's still some digging to be done to find the exact root cause. > Rerendering the text input component by...

> Maybe it is a bug in the TextInput component itself or intended behavior. In that case, we should fix it in `react-native` itself. If there's abug in react-native, this...

@khaterdev, I still don't think not using the `value` prop is the best approach here. There are a bunch of textInputs in our app that use it, refactoring all of...

@deetergp, new documentation also has a [controlled input](https://react.dev/reference/react-dom/components/input#controlling-an-input-with-a-state-variable) section. My point is there's nothing inherently wrong with using value and onChange (i.e. controlled input). Using an uncontrolled input would resolve...

> If you don't need to use a controlled input (for this specific case) and the application works perfectly without it, why are you trying to use it? Because the...