Closed rzfzr closed 11 months ago
I am experiencing the same issue by passing the Button component to the Link component
Does anyone has updates on this topic? I am experiencing the same issue and it's pretty sad that we can't use a custom functional component inside the Link component.
I have the same issue experience by passing the Button component to the Link component. I use a Button from https://reactnativeelements.com/docs/next/components/button
Should be fixed in version 5.11.1
Updates on this? TouchableRipple still has the same problem.
Updates on this? TouchableRipple still has the same problem.
@rollingmoai are you on 5.11.1? If so it might require an additional fix...
Yes, only the button component is fixed.
@rollingmoai try v5.11.2
Can confirm it now works. Thanks for the quick fix!
ListItem has not yet been fixed
@vadolasi Can you try v5.11.6
Experiencing this problem on the Card component. Each card should be able to route me to the dynamic route when clicked. Using "react-native-paper": "5.12.3",
Updates?
Facing same issues for Box component. IconButton
I seem to be getting the same issue with TextInputOutlined
. TextInputFlat
isn't wrapped either. But TextInput
is.
Same issue for Chip.
Same story
<Controller
name="phone"
control={control}
rules={{
required: {
value: true,
message: "Phone is required"
},
pattern: {
value: /^[0-9]{9,15}$/,
message: "Invalid phone number"
}
}}
render={({ field: { ...field } }) => (
<CrystalPhoneInput
{...field}
isPale
/>
)}
/>
Current behaviour
When using a Button, I get the following error.
Expected behaviour
Not have that error?
How to reproduce?
Here's my package.json
Your Environment