[Isomorphic]

This was a bug in some internal code that determines whether a given date-string includes a valid time-portion. We've fixed it for builds dated May 7 and later.

[stonebranch1]

Thanks!

By the way, I just found a work around as well. Turns out if I explicitly call and set the same formatter and parser on the RelativeDateItem that I am setting on the DateUtil, it all works.

Adding this code works:

DateUtil.setNormalDatetimeDisplayFormatter(ClientUtils.getDateTimeFormatter());
DateUtil.setShortDatetimeDisplayFormatter(ClientUtils.getDateTimeFormatter());
DateUtil.setDateParser(ClientUtils.getDateParser());

// code below makes RelativeDateItem work for our formatting/parsing
RRelativeDateItem relativeDateItemProperties = new RelativeDateItem();
relativeDateItemProperties.setDateFormatter(ClientUtils.getDateTimeFormatter());
relativeDateItemProperties.setDateParser(ClientUtils.getDateParser());
RelativeDateItem.setDefaultProperties(relativeDateItemProperties);

This is the same formatter and parser we set in DateUtil and yes we set them before anything is ever constructed.

[Isomorphic]

Yes, the buggy auto-detection logic wouldn't have run in this case.