datePickerModeAndroid="calendar" not working at least in API 24

System: OS: Windows 10 CPU: (4) x64 Intel® Core™ i7-5500U CPU @ 2.40GHz Memory: 2.04 GB / 15.88 GB Binaries: Node: 8.11.1 Yarn: 1.12.3 npm: 6.1.0 SDKs: Android SDK: Android NDK: 16.1.4479499 IDEs: Android Studio: Version 3.5.0.0 AI-191.8026.42.35.5791312

Platforms

Android

Versions

• Android: Simulator 7.0 API 24
• react-native-modal-datetime-picker: 7.5.0
• react-native: 0.60.5
• react: 16.8.6

Description

I want to use Calendar Style for the DatePicker. However, after setting datePickerModeAndroid=“calendar” The style of the date picker is “spinner”. In some device (API 8.0) works the “date” mode like a charm. I think that the component is getting the default value and not what I set. This is the component:

<DateTimePicker
    datePickerModeAndroid="calendar"
    mode="date"
    isVisible={this.state.isCalendarVisible}
    onConfirm={date => this.updateAgenda(date)}
    minimumDate={minDate}
    date={selectedDate}
    maximumDate={maxDate}
    onCancel={() => this.hideAgenda()}
  />

I would like to know how to change the mode to “date” so I can see the picker like this:

Thanks!

[mmazzarolo]

Yes, of course. I did it. It is not related to this library.

@fgagneten gotcha, thanks for reporting.

However, it would great considering a workaround to solve this problem and make it transparent for us. Probably using some style or a custom class using native code.

I’m sorry but it’s out of the scope of this library 😞 In react-native-modal-datetime-picker we won’t mess around with native code.
The issue should be solved directly on the library that handles the picker (which can be react-native or the @react-native-community/react-native-datetimepicker).
If you know a solution for the issue at native level I would suggest you to start a discussion in these libraries. Otherwise, if you know a valid workaround, we can add it to the README.md 👍

[fgagneten]

Yes, of course. I did it. It is not related to this library. However, it would great considering a workaround to solve this problem and make it transparent for us. Probably using some style or a custom class using native code. Thanks