Anusha

@hoangzinh I’ve spent more time investigating this today, but I haven’t yet pinpointed the exact recent change that caused this error. However, I believe the root cause is related to...

Yes, adding the code below in `inputCallbackRef` works. However, I'm still unable to pinpoint the exact recent change that introduced this bug ``` if(!ref){ return; } ```

@hoangzinh I still believe we should remove `updateMultilineInputRange` from [here](https://github.com/Expensify/App/blob/a3a270d918f2130baab4ddc0ddc00a6ddfe7388f/src/pages/tasks/NewTaskDescriptionPage.tsx#L87) and stick with `useAutoFocus`, as we've already incorporated the same logic from `updateMultilineInputRange` into `useAutoFocus`. It would be more logical...

## Proposal ### Please re-state the problem that we are trying to solve in this issue. Back button on issue card page returns to Bank account verified page ### What...

@situchan, I'd like to point out that we rarely use `CONST.NAVIGATION.TYPE.UP` in our codebase—only in two places outside of `goBack`. For cases like this, we generally use `goBack` or `dismissModal`,...

> There's one more verifying step after #51407 so the repro step should be updated a bit. Actually, the user will either see `Got it` or `One more step`, as...

@situchan Another very similar flow in our app is the upgrade process, where after pressing `Got it` to open the NetSuite page, we first dismiss the modal and then navigate...

@situchan Thank you so much.

As I mentioned previously, my approach is widely used across the app. For example, in this similar case [#51883](https://github.com/Expensify/App/issues/51883#issuecomment-2455613641), this pattern was applied. I can provide many more examples if...

> To solve any issue properly, I think we should not depend on whether the solution is used in other places, but based on the correct RCA and verify whether...