[database] FIREBASE WARNING: Invalid query string segment: #517

jc275 · 2018-02-16T18:27:14Z

firebase-js-sdk/packages/database/src/core/util/libs/parser.ts

Line 54 in 5038cec

warn('Invalid query string segment: ' + segment);

@tonymeng This warning now appears during firebase.initializeApp(config) even where config.databaseURL does not include any ns query parameter.

The text was updated successfully, but these errors were encountered:

google-oss-bot · 2018-02-16T18:27:15Z

Hey there! I couldn't figure out what this issue is about, so I've labeled it for a human to triage. Hang tight.

google-oss-bot · 2018-02-16T18:27:15Z

Hmmm this issue does not seem to follow the issue template. Make sure you provide all the required information.

tonymeng · 2018-02-16T18:46:00Z

I'll take a look

benoj · 2018-02-17T14:30:40Z

I have been seeing this too - the query has been running extremely slowly too. Could this be the cause of the slowdown?

The query is

admin.database().ref(`careers/listing-content/${organisation}`).once("value")

and the data in this query only contains 800bytes of data but is taking over 2 seconds to return?

Zjaaspoer · 2018-02-17T15:24:46Z

the query has been running extremely slowly too

seeing this too unfortunately

ysk8 · 2018-02-17T16:01:00Z

I just get this too, but the info about the Warning is incomplete. The function run well, but there is some delay compeers to the nominal speed of Firebase.

harsh183 · 2018-02-17T17:01:59Z

I've been getting this for a bit too on my server. What seems to be causing this? It also seems to cause some slowdowns as well.

mrgoodrich · 2018-02-18T01:54:14Z

+1

Ashok-Varma · 2018-02-18T03:48:43Z

+1

sejr · 2018-02-18T04:10:28Z

+1 😦

mrgoodrich · 2018-02-18T08:50:49Z

I'm a Software Developer at Google and submitted another issue to investigate this problem a few hours ago. Sorry about the frustration, I wish I was familiar with this domain, and it probably won't help to submit more reports fyi. While a fix may have been made, it might not be present in npm or could have not actually fixed the problem. I will also consider contacting @tonymeng (made a change earlier) tomorrow if we don't hear a response, since this seems significant.

ayushmittal · 2018-02-18T09:34:03Z

+1

mrgoodrich · 2018-02-18T17:45:47Z

After talking with support this doesn't seem as serious as I thought. The message is just a warning and "shouldn't have any impacts on the function's overall processing." I thought it was preventing changes to functions, but after viewing the function source in the Cloud Console I see the deployments still succeed. I'll keep you updated if I learn anything else. The fix has not been released, but it has been made.

harsh183 · 2018-02-18T21:04:12Z

All my functions seem to work fine, and it was not preventing that. This is not a critical bug, but it creates a lot of high level warnings that drown out the other logs.

kleeb · 2018-02-18T22:19:06Z

+1

mrgoodrich · 2018-02-18T22:48:39Z

My functions are working again and I was just unlucky with experiencing another problem causing my functions to fail at the exact same time as this warning.

For anyone wanting to remove the warning, in case it has other associated problems, you can force a dependency of "@firebase/database": 0.1.9. I tested this earlier. Also, if they choose to add the bug fix to the next release, I assume 0.1.11+ will not have the warning.

dmurawsky · 2018-02-19T04:23:12Z

+1

marudits · 2018-02-19T05:01:38Z

+1

egr-ext · 2018-02-19T09:06:41Z

Hi, thanks for the support. Is the solution would be to configure the functions/package.json file like that:

{
  "name": "functions",
  "description": "Cloud Functions for Firebase",
  "dependencies": {
    "firebase-admin": "~5.8.1",
    "firebase-functions": "^0.8.1",
    "@firebase/database": 0.1.9
  },
  "private": true
}

jemshit · 2018-02-19T11:40:06Z

Why is this closed ? @tonymeng

egr-ext · 2018-02-19T13:31:45Z

+1 I still have a lot of warning today.

mertkahraman42 · 2018-02-19T19:45:52Z

+1

lanchana · 2018-02-19T21:09:17Z

+1

alexanderkhitev · 2018-02-19T21:32:15Z

+1

tonymeng · 2018-02-20T03:35:51Z

this issue has been auto-closed as the fix has been merged, it will be available in the next version of the sdk.

as for what the issue is, there's a bug in parsing the databaseURL which causes the warning to be logged every time a new connection is made. It should not impact any part of the SDK or connectivity as the query string isn't currently being used for anything.

fethi16 · 2018-02-20T08:26:45Z

+1

lfernando-silva · 2018-02-20T11:42:46Z

+1

mauricioA0 · 2018-02-20T15:46:25Z

I have the same problem.

Do you know when will fix this issue ?

Thanks

di9it · 2018-02-20T15:59:50Z

you can ignore it until next update...

        if (parseInt(firebase.SDK_VERSION.replace('.', ''), 10) === 410) {
            console.ignoredYellowBox = ['FIREBASE WARNING: Invalid query string segment:'];
        } else {
            console.error('REMOVE ME!');
        }

jamatsui · 2018-02-20T16:37:04Z

+1

kclay · 2018-02-20T17:07:12Z

+1

jshcrowthe · 2018-02-20T17:58:21Z

Hey y'all!

Appreciate all the interest in having this resolved. As the fix has already been merged it'll be released in the next version of the SDK. If you are anxious for a workaround:

Consider downgrading to @firebase/database@0.1.9, this version does not contain the bug (and the associated query param support)
Look at the firebase@next package (contains the next staged release, this can fall behind a mainline branch as it is only used to stage the next release get on @latest ASAP after the version has been released)
Look at the firebase@canary package (which will always contain the latest valid code).

NOTE: The NPM canary tag is experimental, if you do opt for the second workaround, make sure you get back onto a mainline release ASAP

kleeb · 2018-02-21T16:36:58Z

how about 0.1.11-0 ?

jshcrowthe · 2018-02-21T17:47:20Z

@kleeb That will also work, that is the next staged version and wasn't released when I wrote the above comment. I'll revise it 😄

mauriciovillalba · 2018-02-21T17:50:36Z

Do you know when will be release the new version ?

lemartva · 2018-02-22T04:35:07Z

Same error here any idea?

jernejc · 2018-02-22T15:22:04Z

+1

salifukayta · 2018-02-22T16:00:54Z

+1

suenwl · 2018-02-22T16:21:33Z

+1

sennl · 2018-02-22T20:32:31Z

+1

amaini · 2018-02-22T21:59:25Z

what is the command to downgarde the firebase
is it npm install --save firebase@firebase/database@0.1.9
please help

kleeb · 2018-02-22T22:26:02Z

0.1.11 has just been released

kleeb · 2018-02-22T22:37:55Z

The warning still occurs on 0.1.11 version

jshcrowthe · 2018-02-22T22:51:38Z

@kleeb can you please try clean installing your dependencies. I just tested this myself and it seems to be working. The behavior I found was the following:

Complete database URLs, with no query params (i.e. https://<PROJECT>.firebaseio.com), do not trigger the warning
Complete database URLs, with a query param set to a value (i.e. https://<PROJECT>.firebaseio.com?foo=bar) do not trigger the warning
Complete database URLs, with a query param that is not set (https://<PROJECT>.firebaseio.com?foo) do trigger the warning (NOTE: This is intended)

tjkang · 2018-02-22T23:51:05Z

finally fixed it with 0.1.11 version! it removed warning for me

mikehlee21 · 2018-02-23T06:28:37Z

Warning has gone away completely on latest version.

"dependencies": {
    "firebase-admin": "^5.9.0",
    "firebase-functions": "^0.8.1",
  },

kleeb · 2018-02-23T08:01:37Z

@jshcrowthe
I am always cleaning out.

I guess that firebase function cache didn't catch it minutes after the release. I redeployed right now and yes - now it is fixed. Thanks!

- Instance of 'class' rather than 'className' in TaskList jsx - Added key to the tr and nested td in the map function that renders tasks - Removed re-base and did a fresh install with 'yarn remove re-base', 'yarn add re-base'. While still functional, old version of firebase was throwing console errors. (see firebase/firebase-js-sdk#517)

frdrcklopez · 2018-02-26T19:36:06Z

first run "npm uninstall @firebase/database"
then "npm uninstall @firebase/database@0.1.8" does the trick to me :)

google-oss-bot added the needs-triage label Feb 16, 2018

jc275 changed the title ~~FIREBASE WARNING: Invalid query string segment:~~ [database] FIREBASE WARNING: Invalid query string segment: Feb 16, 2018

jc275 mentioned this issue Feb 16, 2018

Support ns queryparam #496

Merged

tonymeng mentioned this issue Feb 16, 2018

Fix query string parsing #518

Merged

tonymeng closed this as completed in #518 Feb 16, 2018

firebase locked and limited conversation to collaborators Oct 23, 2019

[database] FIREBASE WARNING: Invalid query string segment: #517

[database] FIREBASE WARNING: Invalid query string segment: #517

Comments

jc275 commented Feb 16, 2018 • edited Loading

google-oss-bot commented Feb 16, 2018

google-oss-bot commented Feb 16, 2018

tonymeng commented Feb 16, 2018

benoj commented Feb 17, 2018 • edited Loading

Zjaaspoer commented Feb 17, 2018

ysk8 commented Feb 17, 2018

harsh183 commented Feb 17, 2018

mrgoodrich commented Feb 18, 2018

Ashok-Varma commented Feb 18, 2018

sejr commented Feb 18, 2018

mrgoodrich commented Feb 18, 2018 • edited Loading

ayushmittal commented Feb 18, 2018

mrgoodrich commented Feb 18, 2018 • edited Loading

harsh183 commented Feb 18, 2018

kleeb commented Feb 18, 2018

mrgoodrich commented Feb 18, 2018

dmurawsky commented Feb 19, 2018

marudits commented Feb 19, 2018

egr-ext commented Feb 19, 2018 • edited Loading

jemshit commented Feb 19, 2018

egr-ext commented Feb 19, 2018

mertkahraman42 commented Feb 19, 2018

lanchana commented Feb 19, 2018

alexanderkhitev commented Feb 19, 2018

tonymeng commented Feb 20, 2018

fethi16 commented Feb 20, 2018

lfernando-silva commented Feb 20, 2018

mauricioA0 commented Feb 20, 2018

di9it commented Feb 20, 2018

jamatsui commented Feb 20, 2018

kclay commented Feb 20, 2018

jshcrowthe commented Feb 20, 2018 • edited Loading

kleeb commented Feb 21, 2018

jshcrowthe commented Feb 21, 2018

mauriciovillalba commented Feb 21, 2018

lemartva commented Feb 22, 2018

jernejc commented Feb 22, 2018

salifukayta commented Feb 22, 2018

suenwl commented Feb 22, 2018

sennl commented Feb 22, 2018

amaini commented Feb 22, 2018

kleeb commented Feb 22, 2018

kleeb commented Feb 22, 2018

jshcrowthe commented Feb 22, 2018

tjkang commented Feb 22, 2018 • edited Loading

mikehlee21 commented Feb 23, 2018

kleeb commented Feb 23, 2018

frdrcklopez commented Feb 26, 2018

jc275 commented Feb 16, 2018 •

edited

Loading

benoj commented Feb 17, 2018 •

edited

Loading

mrgoodrich commented Feb 18, 2018 •

edited

Loading

mrgoodrich commented Feb 18, 2018 •

edited

Loading

egr-ext commented Feb 19, 2018 •

edited

Loading

jshcrowthe commented Feb 20, 2018 •

edited

Loading

tjkang commented Feb 22, 2018 •

edited

Loading