Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TextInput right operand of 'in' is not an object #4294

Open
nimeshmaharjan1 opened this issue Jan 22, 2024 · 7 comments
Open

TextInput right operand of 'in' is not an object #4294

nimeshmaharjan1 opened this issue Jan 22, 2024 · 7 comments
Labels

Comments

@nimeshmaharjan1
Copy link

Current behaviour

Getting this, "Right operand of 'in' is not and object" error after when using the TextInput component from react native paper. If I remove the TextInput component the app works fine. The TextInput from react-native is working though

How to reproduce?

Just a newly created expo project with react native paper and rendering the TextInput component

Preview

image

Your Environment

software version

| react-native | 0.73.2
| react-native-paper | 5.12.1
| expo sdk | 50.0.1
| react | 18.2.0

@AnMiZa
Copy link

AnMiZa commented Jan 23, 2024

Hey @nimeshmaharjan1 can You share Your TextInput code that causes that error?

@nimeshmaharjan1
Copy link
Author

Hey @nimeshmaharjan1 can You share Your TextInput code that causes that error?

It doesn't highlight the TextInput as an error but if I have the TextInput component then the above error is shown

@harbouli
Copy link

The same Issue TextInput from react native paper not working

@Aztaro97
Copy link

I'm facing the same issues with Searchbar components using Expo SDK 50.0.2

@Aztaro97
Copy link

Aztaro97 commented Feb 3, 2024

@nimeshmaharjan1 , I was able to fix the problem after following this 👉 solution #756

@TAQ2
Copy link

TAQ2 commented Mar 11, 2024

@Aztaro97 sorry I'm a react native noob - how would you apply the fix? don't we need to wait until react-native-paper update their nativewind dependency?

@gyanbhartip
Copy link

Could someone please explain why does this fix work? Even if short-circuiting is used, it would return a false instead of undefined (after the solution). But Does react-native not accept false as a value in style array? Why would it fail?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants