Can microsecond precision be kept in firestore_web?

[ditman]

As seen in this bug, when converting Firestore Timestamps to a web DateTime, the code is just using milliseconds. See code here, and here, losing microsecond precision if written by a mobile client.

However, it seems that DateTime may support fromMicrosecondsSinceEpoch (docs) and the JS Timestamp seems to store up to nanosecons for Timestamps (code). It also has a constructor that allows Timestamps to be created from seconds + nanoseconds.

Would it be possible to keep microsecond precision for Timestamps in the the web implementation of Firestore?

[Constans]

I stumbled upon this issue as I'm using the Timestamp to DateTime and the millisecondsSinceEpoch as part of the encryption key used to decode some data. The solution/hack is to retry decoding and makeup for the variation of the value on milliseconds (+/-1).

The issue seems to be happening only on Flutter web. On mobile it works fine.

Not a great solution but with this approach it manages to decode the encrypted data after 3 max retries. Sometimes it works with the 1st run.

Still an issue after 3+ years...