".info/serverTimeOffset" does not work anymore

[l2aelba]

[REQUIRED] Describe your environment

• Operating System version: Browsers
• Browser version: All
• Firebase SDK version: 6.3.3
• Firebase Product: database

[REQUIRED] Describe the problem

I am using .ref('.info/serverTimeOffset') for getting servertime's offset.
But seems like an update I upgrade from v5 to v6 it does not work anymore

Steps to reproduce:

Try code below. It just still waitting...

Relevant Code:

const getServerTimeOffset = await firebase.database().ref('.info/serverTimeOffset').once('value')
console.log(getServerTimeOffset)

[l2aelba]

Oh I found this and its work after I downgraded to 6.2.3

https://firebase.google.com/support/release-notes/js

[schmidt-sebastian]

@l2aelba Sorry about the trouble. You should now be able to update your build to the latest version.

Let us know if you still encounter this issue and we will re-open this.

[glauberramos]

I believe this issue is still happening, just tested with 6.3.4 @schmidt-sebastian. I can't get any value for firebase.database().ref('/.info/serverTimeOffset')

[schmidt-sebastian]

Just to double check - did you include the slash as in your comment? It should just be ".info/serverTimeOffset" as in the issue description. Thanks!

[glauberramos]

I just tried without the slash now and still can't get any value

[puf]

I just tried this and indeed am unable to get the .info/serverTimeOffset on SDK version 6.* (including 6.3.3). See https://jsbin.com/voqivel/edit?html,js,console

[schmidt-sebastian]

Playing with the snippet above, I was able to get the serverTimestampOffset the first couple of times. I am however now also not able to see its value. I will file an internal bug for us look into this.

[puf]

I'm consistently unable to get the offset with 6.3.*. Before that it seems to work.

[glauberramos]

Hello @schmidt-sebastian, any update on this? It would be nice to have an idea when this will be fixed because it's currently blocking me in using the latest version of Firebase with the encoding issue fixed (#2035). Thanks

[schmidt-sebastian]

I'm currently a bit swamped and am planning on looking at this next week. Note that you should be able to go back a couple of releases, as the underlying issue for #2035 was a regression introduced in UglifyJS earlier this year.

[glauberramos]

Thanks! I will try an older version.