Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Setting maximumDate to null crashes android
See original GitHub issuePlatforms
Android only
Versions
Android
- react-native-modal-datetime-picker: v.7.4.2
- react-native: 0.59.3
- react: 16.8.6
Description
Setting maximumDate to null will crash the android implementation of the datePicker.
Note that setting it to undefined works as it should. Component stability could be improved by doing a check in the constructor of the component.
Reproducible Demo
Install react-native-modal-datetime-picker v 7.4.2. in a react native project.
Import the component on any screen of your app.
Use the component, setting maximumDate to null.
Expected behaviour - no maximum date exists. Actual behaviour - component crashes with nullpointer.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I haven’t tried the native android picker - it might be.
The reason why I reported it here / considered it a bug in this library instead of checking the native implementation is that the behaviour an RN Component should be similar on android and ios given the same input. The fix should be easy, you can essentially just add
props.maximumDate = props.maximumDate || undefinedto your components constructorClosing in favour of #301, which fixes the issue.