javascript – React Native TextInput in ScrollView Not Working – Completely different from Normal Keyboard Points

Drawback Description
I’ve a React Native app with a TextInput part inside a ScrollView that merely would not work correctly. The TextInput seems to render however typing/interplay would not operate accurately. That is NOT the standard keyboard dismissal challenge that is generally requested about.
What I’ve Already Tried
I’ve tried all the usual ScrollView keyboard options that did not work:

   keyboardShouldPersistTaps="dealt with"
   keyboardShouldPersistTaps="all the time"
    keyboardDismissMode="on-drag"
    keyboardDismissMode="none"

Working vs Non-Working Code
✅ This TextInput works completely (in a assessment display):

This TextInput doesn’t work (in job progress screen)

 
   {/* Other content... */}

     {/* JobProgressSection component that contains: */}
   
    
     
    

Component Structure
The non-working TextInput is inside:
ScrollView
└── Main Content View
└── JobProgressSection Component
└── Notes Section View
└── TextInput (doesn’t work)

The working TextInput is inside:
ScrollView (or regular View)
└── Feedback Section View
└── TextInput (works perfectly)
Key Differences I Notice

Component nesting: The broken one is inside a separate component (JobProgressSection) that’s rendered within the main component
ScrollView complexity: The broken one has more complex ScrollView props
Styling: Different style objects being used

Questions

Is there something about rendering TextInput inside imported components within ScrollViews that causes issues?
Could the complex ScrollView props be interfering with TextInput functionality?
Are there any known issues with TextInput state management when the component is deeply nested?
Could Firebase real-time listeners or useEffect hooks be interfering with TextInput?

What I Need
I need to understand why one TextInput works perfectly while the other doesn’t, despite both having similar props. The standard keyboard persistence solutions don’t apply here since this seems to be a deeper React Native rendering or state management issue.
Any insights into what could cause this difference in behavior would be greatly appreciated!