I'm coming back into using Firebase after about 2 years, and now I'm having trouble trying to login my CLI into Firebase (yes, I have installed npm i -g firebase-tools). I've tried 3 different commands for it, all of them result in one of the images below:
firebase login
firebase login:ci
firebase login:ci --no-localhost
Here is the result, after I allow Firebase CLI to integrate with my account:
I had already tried this 1 month ago on a Windows machine, but now I'm getting it again on my ArchLinux. Does anyone even have a clue about what's going on? I am logged in successfully on the browser, so I guess it's a problem on Google's end, with an incredibly generic error message.
Just found out someone else has had the same problem yesterday.
I've also registered this as a bug on the respective repo on Github.
And here is what appears on my Inspector's Console, 2 improvement issues:
I don't know why or how, but opening the link through Chrome (or another browser?) actually worked. I was opening it through Brave, thinking that, since both are based on the Chrome engine, nothing would change.
Try using the incognito mode or private tab. I was using Firefox and I get this error. But it worked when I tried in a Private tab.
Related
I'm coming back into using Firebase after about 2 years, and now I'm having trouble trying to login my CLI into Firebase (yes, I have installed npm i -g firebase-tools). I've tried 3 different commands for it, all of them result in one of the images below:
firebase login
firebase login:ci
firebase login:ci --no-localhost
Here is the result, after I allow Firebase CLI to integrate with my account:
I had already tried this 1 month ago on a Windows machine, but now I'm getting it again on my ArchLinux. Does anyone even have a clue about what's going on? I am logged in successfully on the browser, so I guess it's a problem on Google's end, with an incredibly generic error message.
Just found out someone else has had the same problem yesterday.
I've also registered this as a bug on the respective repo on Github.
And here is what appears on my Inspector's Console, 2 improvement issues:
I don't know why or how, but opening the link through Chrome (or another browser?) actually worked. I was opening it through Brave, thinking that, since both are based on the Chrome engine, nothing would change.
Try using the incognito mode or private tab. I was using Firefox and I get this error. But it worked when I tried in a Private tab.
As of 1 day ago, I seem to have trouble with google sign in running inside a flutter app on firebase.
When loading the webapp, I see an exception with obfuscated stack traces:
Uncaught TypeError: t.gpT is not a function
at Im.$1 (google_sign_in_web.dart:113)
at Object.a4P (js_helper.dart:1060)
at Object.Yq (core_patch.dart:84)
at a6F (js_patch.dart:541)
at js_patch.dart:519
at e.zo (cb=gapi.loaded_0:200)
at lk (cb=gapi.loaded_0:203)
at gk (cb=gapi.loaded_0:203)
at _.Rj.hU (cb=gapi.loaded_0:203)
at Qj (cb=gapi.loaded_0:195)
This happens when deploying on firebase and on Chrome, not when running on localhost (same chrome), or when using the firebase deployment on Safari.
I'm properly stumped - I don't remember having upgraded the browser or changing anything in the code. Neither do I remember having fiddled with the oauth tokens.
Any ideas how to properly debug this ? I'm fairly inexperienced in dart/firebase/JS.
[Update]: I found that I can reproduce this even with the Google provided example at:
https://github.com/flutter/plugins/tree/master/packages/google_sign_in/google_sign_in/example
This works when I run it with flutter run -d chrome or flutter run -s web-server
When I do a firebase deploy, the app runs fine in Safari. In Chrome I get above exception. I tried to disable all extensions, same thing.
Aha! The culprit here was blocking of third party cookies. If I turn off third party cookie blocking, things work fine.
Yikes, this makes using Google-sign-in unusable for webapps whose customers are blocking third party cookies.
I don't know is this is the place to ask or even if this is a VC issue.
I am using firebase cloud messaging.
The page works fine and the messaging works as expected
However, when I debug the page in VCODE using F5 or SHIFT F5 the notifications are blocked
Has anyone got any recommendations where I can start looking
So far I have reinstalled both CHROME and VSCODE with no success
Thanks
OK, so I found the issue.
It was the configuration of the launch.json file
I had to include "port":443, in it
I have no idea how it changed
I have used Expo a few times successfully before, but for a few days now, I am unable to get into the Expo App. Whenever I open it, I see the Expo icon for a few seconds up to even minutes, and then it redirects me to the blue "Something went wrong" screen, as if I had tried to open an app.
But I didn't! It doesn't even let me scan a QR code, it just always shows this error. If I click the back button in the app, it simply terminates. I have ensured that it is the latest version and already reinstalled it once.
It seems like it somehow had locked itself onto an old, now non-existant server, and kept at it after reinstalling the app. Here is how I solved the problem:
In the metro bundler, choose connection type "Tunnel" and copy and send the URL to your phone. If you then click on it on your phone, it should redirect to the expo app. After that it got unstuck and I could finally use it normally with the QR code again!
The tools sometimes do get locked into this state.
Close and restart all components (Expo cli, browser tabs and clients) making sure to:
Kill any stray processes on the server (you need to check Activity Monitor / Process Explorer or similar depending on your platform)
Force quit all client devices and simulators using the correct method for each platform. To verify that the client process has actually been killed, check that the app splash screen is displayed for a short while when invoking it.
Clear the Expo cache when starting again: $ expo start --clear
I ran into the same issue. Solved it by going to the left sidebar in the Metro Bundler and sending a link via email!
I've tried many of the solutions and only one worked for me (which i found trying random things). I already had 'allow display over other apps' turned on (Android/OnePlus 6t) and didn't think it had anything to do with that. But I tried this...
Close the Expo app, go the the app settings and turn off 'allow display over other apps', open the expo app and [when prompted] turn on 'allow display over other apps' again.
That seems to work in my case - at least until the next time.
I have searched around and have not found the particular answer that I am seeking for. I just went and updated my App to a Swift 3 Language from swift 2. It obviously threw out a host of errors which I went through and fixed to the best of my abilities and now I do not have any errors. I can run the app but I cant tell if anything else is working because the Login or Auth sections of the app are not working. I know that I can just bypass to test but I have been working on it a lot and trying to get this feature to work that worked well before the language was changed..
Very simple my question is this:
I upgraded to Swift 3. Do I need to upgrade the cocoa pods to support the change in language? If not is it just an issue with the way that my code is and because of the change to swift 3 that i need to keep tinkering with?
Thanks for any help
sorry posted that about 12 hours to early. After doing a lot of research it looks like I found the answer. have not tested yet but I think I am getting the same errors in the compiler.
"We've noticed what seems to be an issue with the latest iOS 10 simulators (up to beta 6 at the time of this writing) that causes Firebase Auth to throw an error due it to not being able to write values to the keychain. This issue does not affect real devices." This is from a Firebase Blog
Hello I got this problem on the device and not on simulator, my device is iOS 9.3.3 and the strange thing is that when run from xcode it works just fine
But when I open from device after stopping debug from xcode, the error will occur
And after some digging, I found out that if pod is only using firebase, it connect just fine even opening from the device
But if I add just 1 pod, it will error like above, so I don't really understand what is going on
And yes already try using keychain sharing
Any tips?
Edit: it works fine on other devices running iOS 8.1