IOS is crashing

[AndonMitev]

Stack:

"@react-native-community/datetimepicker": "6.7.3",
"react-native": "0.71.7"
"expo": "~48.0.15",

Application is just crashing on iOS simulator and physical. No problem with android so far. Any suggestions what could resolve the issue

And this is the code that i'm using:

<HStack alignItems="center" justifyContent="space-between" bgColor="muted.50" px={2} height={50} borderRadius={12}>
    <Text color="textdark.tertiary" fontSize={12}>
      Date of birth*
    </Text>
    <RNDatePicker
      value={value ? new Date(parseInt(value)) : new Date()}
      onChange={(event) => {
        if (event.type === 'dismissed') {
          return;
        }
        const timestampAsStr = event.nativeEvent.timestamp?.toString() ?? '';

        setValue('dateOfBirthTS', timestampAsStr);
      }}
    />
  </HStack>

[RyanGst]

i'm having a similar issue, preventing re-renders on the component (in my case, memoizing the value prop) helped. I haven't fix this issue yet.

two things may help:

1 - datetimepicker version should be at least 7.0.1 to be used with RN 0.70+
2 - Base options typing was updated on e3c05a8

edit:
Take a look at your align styles

[mduc-dev]

i have some issue here is
Invariant Violation: requireNativeComponent: "RNDateTimePicker" was not found in the UIManager.
"@react-native-community/datetimepicker": "^7.1.0",
"react-native": "0.71.7",
i found a few similar cases but everything is not working, trying to link in pod file or remove Pods folder..

[github-actions]

👋 @AndonMitev, sorry you're having an issue. This issue is being closed because it does not provide all information required by the issue template. As the issue template explains, we require that you provide a runnable example that reproduces your issue and your environment information. This means you need to provide a code snippet that we can copy-paste into an empty project and see the error ourselves, or provide a git repository with the issue.
The reason is that maintainers do not have time to try reproduce bugs themselves. Please try to minimize the superfluous code and focus only on reproducing the bug.
Please create a new issue with this and we'll be happy to review it!