Same problem!

For now I just display empty text instead of removing <Text> component. Not sure if that's a suitable solution for you @saracallaioli

The issue is that you try to render an empty string outside a Text component:

{state.error &&
    <Text>
        Some text
    </Text>
}

If state.error is an empty string (falsey value), this transforms into {''}. And you can't render an empty string ('') or zero (0) outside of Text component. But all other falsey values will do. Try to turn this into another falsey value.

For example (null):

{state.error
    ? (
        <Text>
            Some text
        </Text>
    )
    : null
}

or (false)

{!!state.error &&
    <Text>
        Some text
    </Text>
}

Also seeing this issue. Causing major issues on the app after upgrading. Seems to be largely for Android.

Same here, with the added problem that the error/stacktrace doesn't show which files of my project contain the issue making it very hard to fix :/

I have this issue as well, only on Android. And I couldn't find any problem with my TEXT!!

We're having the same problem here too :( and no way of easily seeing which file is causing it

I had a semi colon somewhere it shouldn't have been. return <View><Text>Hi!</Text>;</View>;

I have same problem too. Over one day =.=

I've had the same problem for a while until I realized that in order to make a line break between 2 paragraphs, I had this {`\n`} between 2 Text components. Removing it fixed this issue for me

Same here. Fixed by removing texts that was outside the <Text> tag

Issue was fixed for me by removing a space I had between my tags.

By the way, I've just noticed, that this error message actually shows a text that caused it (notice Test text).

on android, do not use { your_condtion && <YourComponent/ >}