Description
When navigating to /search, a red error toast appears at the bottom of the screen showing:
"Unexpected text node: . A text no..."
This is a React Native Web rendering issue where a bare text node (not wrapped in a <Text> component) is present in the Search page component tree.
Steps to Reproduce
- Navigate to
http://localhost:8081/search
- Observe the red error toast at the bottom of the page
Expected Behavior
No error toast should appear. All text content must be wrapped in <Text> components per React Native requirements.
Actual Behavior
Red toast: "Unexpected text node: . A text no..."
Impact
- Severity: Low (cosmetic, doesn't block functionality)
- Page:
/search
- Component: Likely in search page or one of its child components
Environment
- Frontend: Expo web (React Native Web)
- Browser: Chrome
- Dev mode: Yes
Description
When navigating to
/search, a red error toast appears at the bottom of the screen showing:"Unexpected text node: . A text no..."
This is a React Native Web rendering issue where a bare text node (not wrapped in a
<Text>component) is present in the Search page component tree.Steps to Reproduce
http://localhost:8081/searchExpected Behavior
No error toast should appear. All text content must be wrapped in
<Text>components per React Native requirements.Actual Behavior
Red toast: "Unexpected text node: . A text no..."
Impact
/searchEnvironment