[Exception thrown while executing UI block:-[_ _NSCFString timeIntervalSinceReferenceDate ]: unrecognized selector sent to instance

[ashirkhan94]

In iOS Getting red screen error when render <DatePicker date={new Date()} /> on React Native
But working fine on android
Error:
[Exception thrown while executing UI block:-[_ _NSCFString timeIntervalSinceReferenceDate ]: unrecognized selector sent to instance

• OS: [ iOS]
• React Native version: 0.75.4
• react-native-date-picker version : 5.0.1 or 5.0.10

[kamui545]

Actually nevermind, it looks like 5.0.9 works on debug mode but release mode is still broken... weird.
The 5.0.0 version seems to be fine on both debug / release mode...

I think this is a regression from #894.
I downgraded to 5.0.9 and it works fine.

[mphill]

This happens with the spinner. The modal works, but this is an urgent issue.

[kalfheim]

I'm getting the same error on 5.0.10. Downgrading to 5.0.9 seems to seems to work for now

[themtaysw]

same here (5.0.10)

[laurens-lamberts]

Same here. I can confirm that 5.0.9 does still work for me in debug mode, but 5.0.10 throws the error.
As an earlier comment in this thread mentions issues with 5.0.9 in release mode, I'll rollback a bit further.

Update; 5.0.9 indeed did NOT work for me in a release build, but 5.0.8 seems to work fine in release mode.

[ahmedprusevic]

+1 , this happened tome after upgrading to expo 52 and upgrading react-native-date-picker to 5.0.10 (prev v5.0.9 wasn't working as well)

[jpancotti]

+1 I have found that the issue does not happen in bridgeless mode / new architecture.
Were some changes made in 5.0.10 to support new architecture? If so this seems to have broken spinner in old architecture.

[jchiversAND]

+1 getting same error with 5.0.10 on iOS. Android works fine.

[valentinllpz]

+1 same error with 5.0.10 on iOS + RN 0.76.6

Downgrading to 5.0.9 seems to work

[mortezacruise]

Same here. I can confirm that 5.0.9 does still work for me in debug mode, but 5.0.10 throws the error. As an earlier comment in this thread mentions issues with 5.0.9 in release mode, I'll rollback a bit further.

Update; 5.0.9 indeed did NOT work for me in a release build, but 5.0.8 seems to work fine in release mode.

I downgraded to 5.0.8 and issue solved for me