Because relying on toLocaleString to parse date, time, or date+time to locale language, turned out there was an update and en-US locale uses now " at " as date+time separator compared to previous ", ". This caused problem to parse the time portion.
As any locale can have different date+time separator or the separator can change as it happened now, the current solution wasn't reliable. Instead, I am updating this parsing so it does NOT rely on any date+time separator, which solved the problem.
Because relying on
toLocaleString
to parse date, time, or date+time to locale language, turned out there was an update anden-US
locale uses now " at " as date+time separator compared to previous ", ". This caused problem to parse the time portion. As any locale can have different date+time separator or the separator can change as it happened now, the current solution wasn't reliable. Instead, I am updating this parsing so it does NOT rely on any date+time separator, which solved the problem.