I'm creating a Flutter app with Firebase Authentication. It worked fine first, but now the authentication is super slow the first time. When the user authenticates (either with email or anonymous) the first time, it works fine the next time - sign-out works, re-signing works fine. It's the first time that is slow - it takes several minutes.
I have tried creating a new project in Firebase Console. I have tried upgrading to Blaze plan (from Spark). I have tried re-creating the project. Nothing seems to help.
Any ideas?
It's the issue with the recent versions of Android Emulator on Windows platform. I was using the android emulator version 31.3.10 and had that problem.
Try downgrading the android emulator version to 31.2.9
Link to downgrade - https://developer.android.com/studio/emulator_archive
It doesn't solve the problem at all, running the app on my phone blocks me to connect with my back-end application, waiting for a solution..
Update: see the answer from Hisham Siyed, this is the best solution which worked for me!
I found it out the following:
It worked better when I tried from another Google account for Firebase. For some reason my first account is lagging. Perhaps some quotas are reached, or I'm blacklisted as a robot :). This helped for a while, but I got eventually into the same problem.
Then I found out that it works much better on a physical device. I was using the emulator first. It seems that the Android emulator is having some bugs for Firebase access.
I contacted Firebase support and got a suggestion to use Android emulator with API Level 29. It worked on one PC, did not work on another.
So far the best workaround I found is to use a physical device for testing, not an emulator.
Related
So months ago I was trying to upload my Flutter app to the App Store (it's already on Android) but kept getting rejected because when the Apple testers tried to sign in with Apple on their emulators, it gave an error message. It worked fine on all physical devices. I gave up trying but now I'm back at it and wonder if anyone knows if there is some sort of firebase_auth / flutterfire_ui version combo that happens to work in every situation (apple, google, email sign-in). I've tried the latest versions of each and the issues still exist. If I can't figure this out I will have to write my own sign-in page from scratch, which I would rather not do.
Sounds like a bunch of others are having the same issues. Has anyone experienced anything like this? Thanks!
The app I have created seems to open quite slow (and janky) compared to other apps on my phone. It only seems to happen on android
I have tried copying the dependencies to a new project and running it and it doesn't replicate the same behaviour.
I have also changed the original app to only load a red container in the matierial app but its still really choppy on app launch before it loads.
I would post some code but I am not entirely sure whats wrong.
Sorry this is quite vague but I am running out of ideas. I dont really want to have to recreate everything in a new project.
Please note I have done the android v2 migration so it could potentially be linked to this?
Does anyone have any ideas to what could be causing it?
Update:
Forgot to mention this is on profile/release mode.. its not debug mode causing it
Well, it's hard to know why your app is being so "janky" but i'm going to make a few shots in the dark:
Are you running this on an emulator or on a real phone? Emulators will sometimes act weird, and will deliver results that you might not see on an actual android device. If you are running this on an emulator, try launching it on a physical phone. I have had experience with using Android emulators and sometimes trying to open the app at all becomes weird. How old your phone is might also be the cause of this, if it is old.
Do you have too many tabs open? Try exiting out of all of your applications and then open up your flutter app. See if that does anything.
That is all that I have concerning the environment that you are working in. You haven't posted any code, so i'm going to have to ask you about what your app is doing on startup. It would be good if you posted some code or a link to a git repository so that I can see that and be of better help.
I am creating an android app built with angualar/ionic 5. and currently testing with android studio via enabled debugger on an android device.
The apps works well except for one issue.
The app, when minimized or drawn from the active apps lists restarts instead of resuming to the last active page. I am using angular/ionic 5 and I don't believe this is an issue angular/ionic router since this works fine in pwa/browser versions of the app.
I may be wrong but seems to think this may be due to some missing config for android platforms in config.xml . In my search I came across this
1. <preference name="AndroidLaunchMode" value="singleTask"/> //adding this to config.xml but it did'nt work.
some comments suggested memory leaks may be causing android to shut the app down when it's not in the foreground but tracking the apps memory usage in android studio, it seems to be within acceptable range
My conclusion is that perhaps a problem with ionic/capacitor/cordova core or some bug
This is driving me nuts!
If any one has had this problem, how did you solve it please?. and for those experienced ionic developers . what and where would you be looking at if you this issue. Thank you
I tried a different device on the emulator and it worked also tried a different physical device and it worked. this means that the problem is with my particular device. that leaves a lot of questions since a lot of people use my android brand with similar specifications. will the app exhibit same behaviour when downloaded from the playstore? or this is just an android testing and debugging problem.. i will inform you all of what will come later . thank you
In this case I would suggest you to check your device setting you might have mistakenly added this application in battery optimization mode.
Please check your setting I belive this is the culprits. Not your code
Thanks
Odd one this. Ever since upgrading to iOS10 and the latest Appcelerator SDK (5.5.0), I can't get even a simple console.log("hi!") to show anything in the console when I'm testing on an iPhone 6s Plus connected to my Mac via USB, using LiveView.
I've tried changing it to Ti.API.info("hi!") - which I believe is the old way to do it - to no avail. If I change it to alert("hi!"), that works fine. However, it's not as useful as console.log used to be when developing things which MUST be tested on a connected device (the camera, in my case).
I've Googled this, plus done extensive searching on StackOverflow.
It may be that this is so new that no-one has noticed yet.
Can anyone help?
It's a known issue. Apple changed something with the way they log data. The Appcelerator SDK has to be adapted to this changes. I'm pretty sure they'll fix it asap. You'll have to await an update.
Greetings
Edit: Here is the corresponding jira ticket (https://jira.appcelerator.org/browse/TIMOB-23786)
Our latest app was rejected by giving following reason
"when the user launches the app, a blank black screen is produced"
We had tested this many times and did not notice this issue. We tested again now, but it is working properly for us.
Can someone help us to find out the issue?
I don't think anyone can help you find this issue, My suggestion would be to follow up with the Review Team and try to obtain as much information as you can from them. Such as, what device was it tested on, what OS version and so forth.
Ah, the many woes of the app store process.
Make sure that you have tested your app not only on the simulator but also on a physical device.
Secondly the issue might be that you have made some (false) assumptions about the data on the device, that you might have put there manually, but isn't handled when installing anew.
Therefore a plan of attack might be to remove the application complete from both device and simulator and try running them from a fresh install rather than on top of an already installed installation.
Best of luck!
Try to build and install your app from a clean state. You may not be seeing the same as the reviewer, because if you only "build&run" all the time, old files, which are not part of the final build, are still present on your device or in the simulator.
So clean the build folder, remove the app from your device, and try again. Also, check if you app can live without an internet connection.
Your best bet is to discuss this directly with the Apple guys (Resolution Center).