Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
jc275 opened this issue Feb 16, 2018 · 48 comments
Closed

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

jc275 opened this issue Feb 16, 2018 · 48 comments

Comments

@jc275
Copy link

@jc275 jc275 commented Feb 16, 2018

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.

@google-oss-bot
Copy link
Contributor

@google-oss-bot google-oss-bot commented Feb 16, 2018

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

Loading

@google-oss-bot
Copy link
Contributor

@google-oss-bot google-oss-bot commented Feb 16, 2018

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

Loading

@jc275 jc275 changed the title FIREBASE WARNING: Invalid query string segment: [database] FIREBASE WARNING: Invalid query string segment: Feb 16, 2018
@tonymeng
Copy link
Contributor

@tonymeng tonymeng commented Feb 16, 2018

I'll take a look

Loading

@benoj
Copy link

@benoj benoj commented Feb 17, 2018

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?

Loading

@Zjaaspoer
Copy link

@Zjaaspoer Zjaaspoer commented Feb 17, 2018

the query has been running extremely slowly too

seeing this too unfortunately

Loading

@ysk8
Copy link

@ysk8 ysk8 commented Feb 17, 2018

screen shot 2018-02-17 at 10 57 22

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.

Loading

@harsh183
Copy link

@harsh183 harsh183 commented Feb 17, 2018

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.

Loading

@mrgoodrich
Copy link

@mrgoodrich mrgoodrich commented Feb 18, 2018

+1

Loading

1 similar comment
@Ashok-Varma
Copy link

@Ashok-Varma Ashok-Varma commented Feb 18, 2018

+1

Loading

@sejr
Copy link

@sejr sejr commented Feb 18, 2018

+1 😦

Loading

@mrgoodrich
Copy link

@mrgoodrich mrgoodrich commented Feb 18, 2018

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.

Loading

@ayushmittal
Copy link

@ayushmittal ayushmittal commented Feb 18, 2018

+1

Loading

@mrgoodrich
Copy link

@mrgoodrich mrgoodrich commented Feb 18, 2018

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.

Loading

@harsh183
Copy link

@harsh183 harsh183 commented Feb 18, 2018

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.

Loading

@kleeb
Copy link

@kleeb kleeb commented Feb 18, 2018

+1

Loading

@mrgoodrich
Copy link

@mrgoodrich mrgoodrich commented Feb 18, 2018

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.

Loading

@dmurawsky
Copy link

@dmurawsky dmurawsky commented Feb 19, 2018

+1

Loading

1 similar comment
@marudits
Copy link

@marudits marudits commented Feb 19, 2018

+1

Loading

@egr-ext
Copy link

@egr-ext egr-ext commented Feb 19, 2018

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
}

Loading

@jemshit
Copy link

@jemshit jemshit commented Feb 19, 2018

Why is this closed ? @tonymeng

Loading

@egr-ext
Copy link

@egr-ext egr-ext commented Feb 19, 2018

+1 I still have a lot of warning today.

Loading

@mertkahraman42
Copy link

@mertkahraman42 mertkahraman42 commented Feb 19, 2018

+1

Loading

2 similar comments
@lanchana
Copy link

@lanchana lanchana commented Feb 19, 2018

+1

Loading

@alexanderkhitev
Copy link

@alexanderkhitev alexanderkhitev commented Feb 19, 2018

+1

Loading

@tonymeng
Copy link
Contributor

@tonymeng tonymeng commented Feb 20, 2018

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.

Loading

@fethi16
Copy link

@fethi16 fethi16 commented Feb 20, 2018

+1

Loading

1 similar comment
@lfernando-silva
Copy link

@lfernando-silva lfernando-silva commented Feb 20, 2018

+1

Loading

@mauricioA0
Copy link

@mauricioA0 mauricioA0 commented Feb 20, 2018

I have the same problem.

Do you know when will fix this issue ?

Thanks

Loading

@di9it
Copy link

@di9it di9it commented Feb 20, 2018

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!');
        }

Loading

@jamatsui
Copy link

@jamatsui jamatsui commented Feb 20, 2018

+1

Loading

1 similar comment
@kclay
Copy link

@kclay kclay commented Feb 20, 2018

+1

Loading

@jshcrowthe
Copy link
Contributor

@jshcrowthe jshcrowthe commented Feb 20, 2018

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:

  1. Consider downgrading to @firebase/database@0.1.9, this version does not contain the bug (and the associated query param support)
  2. 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)
  3. 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

Loading

@kleeb
Copy link

@kleeb kleeb commented Feb 21, 2018

how about 0.1.11-0 ?

Loading

@jshcrowthe
Copy link
Contributor

@jshcrowthe jshcrowthe commented Feb 21, 2018

@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 😄

Loading

@mauriciovillalba
Copy link

@mauriciovillalba mauriciovillalba commented Feb 21, 2018

Do you know when will be release the new version ?

Loading

@lemartva
Copy link

@lemartva lemartva commented Feb 22, 2018

Same error here any idea?

Loading

@jernejc
Copy link

@jernejc jernejc commented Feb 22, 2018

+1

Loading

3 similar comments
@salifukayta
Copy link

@salifukayta salifukayta commented Feb 22, 2018

+1

Loading

@suenwl
Copy link

@suenwl suenwl commented Feb 22, 2018

+1

Loading

@sennl
Copy link

@sennl sennl commented Feb 22, 2018

+1

Loading

@amaini
Copy link

@amaini amaini commented Feb 22, 2018

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

Loading

@kleeb
Copy link

@kleeb kleeb commented Feb 22, 2018

0.1.11 has just been released

Loading

@kleeb
Copy link

@kleeb kleeb commented Feb 22, 2018

The warning still occurs on 0.1.11 version

Loading

@jshcrowthe
Copy link
Contributor

@jshcrowthe jshcrowthe commented Feb 22, 2018

@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)

Loading

@tjkang
Copy link

@tjkang tjkang commented Feb 22, 2018

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

Loading

@baymaxdev
Copy link

@baymaxdev baymaxdev commented Feb 23, 2018

Warning has gone away completely on latest version.

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

Loading

@kleeb
Copy link

@kleeb kleeb commented Feb 23, 2018

@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!

Loading

reidangwin added a commit to reidangwin/bloctime that referenced this issue Feb 23, 2018
      - 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)
@effs12
Copy link

@effs12 effs12 commented Feb 26, 2018

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

Loading

@firebase firebase locked and limited conversation to collaborators Oct 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.