datetimepicker | Amaze UI styled bootstrap-datetimepicker | User Interface library

Notice that

Please note that this library currently exposes functionality from UIDatePicker on iOS and DatePickerDialog + TimePickerDialog on Android, and CalendarDatePicker +TimePicker on Windows.

These native classes offer only limited configuration, while there are dozens of possible options you as a developer may need. It follows that if your requirement is not supported by the backing native views, this library will not be able to implement your requirement. When you open an issue with a feature request, please document if (or how) the feature can be implemented using the aforementioned native views. If those views do not support what you need, such feature requests will be closed as not actionable.

as provided in the react-native-datetimepicker documentation.

The date prop that you are using is one of them. For iOS it exposes a field of UIDatePicker which is

The initial date that the date picker will display. Defaults to the current date, but you can set a custom value. This attribute is equivalent to setting the date property programmatically.

However, as stated in the react-native-datetimepickerdocumentation its usage is limited. The correct prop that we need to use is the value prop which

Defines the date or time value used in the component.

This field is required. We cannot unset it. There will always be some default value which needs to be explicitly set initially.

However, what you want to achieve can be done differently. You need to handle the form value yourself in a state of the form. Thus,

Apparently, this is due to com.eightbitlab:blurview being only available from jcenter which is required by react-native-community_blur.

I've added jcenter() in my build.gradle file and it's now working fine.

can you give your

• package.json
• node version

I think that's because of the babel issue / your node version, because it cannot transpile the optional chaining https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining

maybe tried using latest LTS node version? because as far as I know, the latest LTS node version already support optional chaining

You have to create the timestamp in your local timezone first, and then convert it to UTC. You are doing it the other way around. Ie if I split up your code snippet, you are doing the following

You seem to be using Windows cmd to run the command, and hence you are getting the error.

The command:

You can do it by using getState method on persianDatepicker instance, like this:

That will depend entirely on which datetimepicker component you are using.

This one lets you set the maximum view:

Downgrade @date-io/date-fns from 2.11.0 to 1.3.13.

From the installation guide of Material UI Pickers:

Important: For material-ui-pickers v3 use v1.x version of @date-io adapters.