Closed apsdehal closed 4 years ago
I can reproduce, this is a server-side problem. I'll leave this Github issue open until the fix is live.
@apsdehal I would like to check if you are still having this issue. It seems that it was already addressed in the previous releases. I tried reproducing this using the latest version (7.4.0) and it throws 400 as you expect.
Hey @apsdehal. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Since there haven't been any recent updates here, I am going to close this issue.
@apsdehal if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
Steps to reproduce:
Sending
firebase.database.ServerValue.TIMESTAMP
for one of the values in custom metadata throws 503 (Service Unavailable) which is not the right status code for this I think. It should be something on the lines of 400 (Bad request).Relevant Code: