My Flutter app that has a login page is fully functional on Android, iPhone and Web.
The problem is with the WebApp - immediately after I deploy it into the Firebase, it works well, as expected. However, if I leave it and come back to it in several hours, and try to open another window - neither text fields nor mouse user entry are accepted any longer. If I then rebuild the app and redeploy it, it starts working, for a while.
I use flutter version 2.10.5 and Dart version 2.16.2.
Flutter doctor -v produced no errors or warnings.
Has anyone experienced this sort of behaviour?
Related
I am working on an app that uses firebase sign. The application is working perfectly on debug mode but when I release it, the application crashes just after the user as successfully login. Since the application is in release mode, there is no way to monitor the logs so as to tell where the error is coming from.
I was using flutter 2.8 from the stable channel but after reading some of the things said on this post, I decided to upgrade to the latest version of the stable channel but still, nothing works. I will appreciate help.
I have clean and pub get
I have use the "--no-shrink" command
I finally fixed it. I added no shrink command to my build.gradle
We are using Firebase auth on a React Native app using react-native-firebase for several years now (currently at 12.9.3). A few days ago, without a new Android release or changes in the Firebase console, an Android user could login in the morning but then could not any longer in the afternoon and then after and getting this "firebase_auth/missing-client-identifier" error message.
I have searched here and at the react-native-firebase issues at GitHub but could not find any cases that this happens to only one user. Then yesterday, a second user started facing the same problem which is worrisome.
I checked the SHA-1 and SHA-256 fingerprints and everything is setup correctly and that is why thousands of other users are not facing an issue.
Any ideas of what could be causing this?
Thanks!
I'm reporting a very strange problem.
I have an app developed in Flutter and I have correctly integrated the Firebase library for using the Dynamic Links service.
The problem is when short links are open on a mobile device, it shows a screen with the message "Save my place in the app. A link will be copied to continue to this page", and a button OPEN to continue.
Using your link debugging tool everything seems ok
When I develop directly in debugging mode the problem does not present itself.
When I install the app from TestFlight sometimes it works and sometimes it doesn't. It seems random.
the problem could be that the app is not yet available on the store ?
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.
Run App in the iOS Simulator
Go through the login flow and login
Stop App and Remove App from the iOS Simulator
Run App and notice that the cache persists; FirAuth.auth()?.currentUser is the user that I previously logged in with before removing the app.
My assumption that by removing the app from the simulator enables me to start from a blank slate next time I run is not correct.
Can somebody please explain how/why the cache persists?
Firebase manages this internally. The user which you get from FirAuth.auth()?.currentUser has nothing to deal with cache. So, even you delete the app from your simulator you will get currentUser.