-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Datepicker does not open in ios9 #183
Comments
Did you get this resolved? |
Same here. It does not work after I open it once, I cannot open it the second time:
I get the above error when I try opening it again. |
@gaurav-chandra - I think you're issue is that the options should be inside the function that opens the datepicker. :) |
No, the issue was with DatePicker.m file. I changed it to the following commit:
and it worked like a charm. |
gaurav in which line you added inside DatePicker.m file ?? |
@aleximmauell don't know the line but I replaced the whole file. |
@gaurav-chandra : when i replaced whole file and on second firing the datepicker is not working .. |
@aleximmauell this might mean the file has the same old code. The original file had this problem of not opening the datepicker the second time. The fork works for me. You need to check the xcode editor for error highlighting. |
webView:decidePolicyForNavigationAction:request:frame:decisionListener: delegate: Invalid parameter not satisfying: date .......is the error |
The only time I have hit this issue is if I don't pass a date in on the options. In DatePicker.js, if no date is passed in the defaults use "new Date()", and the formatDate() function isn't called. If you pass in a date when calling show() then the formatDate() function is called and iOS doesn't blow up trying to show the picker with the "Invalid parameter not satisfying: date" error message. |
@aoathout : can you able to show the modified code here ... |
@aleximmauell I create a PR for this: |
Date picker does not open in ios9 and gives a assertion failed error in the logs.
The text was updated successfully, but these errors were encountered: