There is a bug that causes the datetimepicker to parse dates wrong (e.g. '2015-10-07T13:00:00Z' is parsed as July 10th instead of October 7th) because the setPickerValue() is using the
ngModelCtrl.$viewValue instead of ngModelCtrl.$modelValue.
This causes the picker to lose the moment object and instead set it to a locale based string format of the original date that is then parsed wrongly.
I have the same issue, when you initialize the model with a date variable it doesn't set the datepicker value, but if you take it from the $modelValue it works fine
There is a bug that causes the
datetimepicker
to parse dates wrong (e.g.'2015-10-07T13:00:00Z'
is parsed asJuly 10th
instead ofOctober 7th
) because the setPickerValue() is using thengModelCtrl.$viewValue
instead ofngModelCtrl.$modelValue
.This causes the picker to lose the
moment
object and instead set it to a locale based string format of the original date that is then parsed wrongly.