It looks fine to me now. That kind of bug looks like a field name changed or was not getting passed through correctly and led to a bunch of "new Date(null)" invocations.
Basically a bad update/fix went out. It seems fine now to me.
It also could have been a two phase update where the UI briefly mismatched with the expected backend data format.
It looks fine to me now. That kind of bug looks like a field name changed or was not getting passed through correctly and led to a bunch of "new Date(null)" invocations.
Basically a bad update/fix went out. It seems fine now to me.
It also could have been a two phase update where the UI briefly mismatched with the expected backend data format.