Hi Sarah,
Thanks for the update.
We have checked the issue based on shared information and suspect that the startDate and endDate values of the DateRangePicker component should have been assigned with the UTC string (along with time zone consideration) due to which the reported issue may occur. This is because, whenever a value in UTC with time zone consideration is processed at the client end, it will get converted based on the client time zone by adding the time zone offset value to the Date value which will result in change of Date values.
In detail, if UTC value 2018-02-12T23:00:00.000Z (2/12/2018 11:00 PM) is processed at client end with zone of UTC+1, the offset value 1 hour will get added to the UTC date value and converts the value as 2/13/2018 for 1 hour added to 11 PM converts the value to next day. Similar case should have been happened in your application. If this is your case, then we request you to pass the date value to the startDate and endDate value by removing the zone factor in the UTC date value as shown below so that the time zone based conversion can be restricted.
2018-02-12T23:00:00.000 instead of 2018-02-12T23:00:00.000Z
If this is not your case, then please revert with the source code for DateRangePicker initialization and values being assigned to the control along with an issue reproducing sample, so that we can validate the issue at our end and provide an exact solution for your requirement.
Regards,
Prem Kumar M