FIREBASE WARNING: Invalid query string segment - Warning when deploying simple Firebase Cloud function

Question

This morning I started noticing a large amount of \"FIREBASE WARNING: Invalid query string segment\" errors in my functions log. In an attempt to figure out wha

Answer 1

Update: It's officially a bug and you can ignore it until they release a fix in the next update or add version of @firebase/database: 0.1.9 to dependencies if you don't want to wait.

---

Seems like an internal error or change. Also getting this firebase warning and my code was working fine yesterday using '' syntax as well. However my function still works. Looks like they're doing some heavy dev work on it as its in beta and issues are coming up now and then.

Wait for fix or report here: https://firebase.google.com/support/contact/bugs-features/

Status here (fixes usually take time to appear on here): https://status.firebase.google.com/

Copy of 48830081 and possibly 48832566

Answer 2

It seems they are having issues with notification. You can check for the status here: https://status.firebase.google.com/

Answer 3

I am new to Firebase today.

The code snippet I generated for the Firebase db connection had this firebase.js :

<script src="https://www.gstatic.com/firebasejs/4.10.0/firebase.js"></script>

This is generating the message : 'FIREBASE WARNING: Invalid query string segment:', but is also returning the data.

If I use a different version of firebase.js, either .../4.8.0/... or .../4.9.0/... , no error/warning message is generated.

I am running Google Chrome on Windows 10.

Answer 4

After talking with Firebase support, I learned this bug was introduced in the npm dependency @firebase/database: 0.1.10. You will have this dependency if you also have the latest firebase-admin dependency.

The warning

shouldn't have any impact on the function's overall processing.

If you want to remove the warning, you can force the npm dependency of @firebase/database: 0.1.9. I tested this adjustment and the warning was removed from my Firebase Console Logs.

The support agent also stated the fix has been made, but not released, so I would expect @firebase/database: 0.1.11+ to not experience this bug.

Answer 5

Looks like a recently introduced bug which will hopefully be fixed soon.

Answer 6

We having the same problem today. Maybe some maintenance in the platform. Maybe some Google dev will soon say something about this.