I was working on a project for my studies and everything was working fine, but I changed my OS to win11 while wiping all previous data.
Now Firebase is stuck on "loading" after using any type of sign in. Real time database data is not showing as well. After around 5-10 of waiting auth will sometimes work continuously (can sign in, sign out multiple times, until running app again) but database never.
Everything works well when i use physical device. Apps without firebase work fine on emulator. Internet connection works. Example app that doesn't work: https://github.com/firebase/quickstart-android
I have:
Used multiple different emulators(those with google play) with different sdk
Changed SHA1 and google-servies.json
In Settings -> Appearance & Behavior -> SDK Tools downloaded and activated Google play service
Reinstalling Android Studio, installing win10 again
Updated Google Play services version
Tried different projects on different firebase accounts
Activated Sign-in methods in firebase console
Searched web for several hours and done many other things I can't even remember now
The only error I'm sometimes getting is: E/FirebaseInstanceId: binding to the service failed
and this error when I use new emulator for the first time: E/FirebaseMessaging: Topic sync or token retrieval failed on hard failure exceptions: java.util.concurrent.ExecutionException: java.io.IOException: AUTHENTICATION_FAILED. Won't retry the operation.
E/FirebaseInstanceId: Topic sync or token retrieval failed on hard failure exceptions: AUTHENTICATION_FAILED. Won't retry the operation.
E/FA: Missing google_app_id. Firebase Analytics disabled.
E/FA: Uploading is not possible. App measurement disabled
For me it looks like something is blocking(or really slowing down) connection between android studio emulator and firebase.
I would be very grateful for any kind of help, its really important for my studies.
What fixed my problem was installing an older version of android emulator form this website:
https://developer.android.com/studio/emulator_archive
I was using Android Emulator (31.3.10) Beta 1 and switching to Android Emulator (30.9.5) solved the problem.
I think it's the emulator... Or at least it was for me. I was working with version 31.3.10 and had the same problem. App would not connect to the Firebase server in the emulator. Firebase Authentication would eventually work but took forever to login. Firebase was only using local data. Queries to Firebase returned results only from the cache (which was empty anyway), and I could see that (QuerySnapshot.metadata.isFromCache was true).
Tried reinstalling the app, deleted the emulator image and made a new one, nothing worked. Internet access on the emulator was fine, I could browse web pages etc.
Only thing that worked was downgrading the emulator. I went back to 31.2.10, cause I knew that one worked. You can get older versions from https://developer.android.com/studio/emulator_archive
I really hope they fix it soon cause it cost me a whole day to figure out wtf. Hope this helps someone else.
I have the same problem. It happened after several updates: Windows and Android Studio. Apparently, it's the emulator (version 31.3.10).
In my case, the solution to the problem is disabling Wi-Fi in the emulator and enabling mobile Internet. Although in fact the connection in Windows remains the same.
I found the solution here. Error in the emulator version 31.3.10. Change the emulator to 30.2.9
https://youtu.be/qo3SbdbXFos
I was using emulator version something like 31.3.10 and upgraded it to 31.3.11. Now problem is solved.
Downgrading will also work but i like upgrading.
Below i have attached the screenshot:
https://user-images.githubusercontent.com/96950460/193184898-28e24140-8b12-4c80-8900-c56d4776619b.png
The problem seems to be the emulator. I updated android studio recently and the code that I had already gotten to speak to firebase stopped working without me editing anything.
Instead of reverting to an older emulator, I switched to using a physical device such as my phone instead.
It fixed it right away.
I have the same issue with emulator 31.3.12. After app startup it can't connect to any Firebase services. After 7 minutes and several retries it worked. Without any interaction from my side.
I am using Firebase Remote Config and Crashlytics.
Related
For a school project we are using auth0 for the authentication of our app, but the login keeps failing for me (for the rest of my group it works if they use the same code as me). We are using a google account to login as an admin but it seems he is getting stuck after I click login (see screenshot). I also don't get any error message.
Screen it gets stuck on when I try to log in
I've tried reinstalling android studio, reinstalled multiple new emulators, recloning the project and so on. The information on the Internet didn't help either.
Edit - fixed
If the rest of your group can run this and it works, this means usually a hardware or software problem on your part. I had same issue, turns out it was software problem on android studio, missing dependencies or other plugins that interferes.
I would say try on another device in case this is hardware problem.
Suddenly from 3 days, I am not able to use Google Internal App sharing. Loading App sharing page fails with error "unexpected error". Is there anyone else who faced this issue? and have some workaround?
Note:
I am aware that I should raise this issue in Google support, but they are taking too much time to respond. Meanwhile, I am just searching for workarounds or possible reasons for it.
I have tried all possible solutions which are already there on the Web, like incognito mode, clearing cache, etc.
In my network those who already have play store accounts are also getting the same issue.
The API gateway still seems to work. I was able to upload a test apk/aab via fastlane.
It's an easy setup. Then use the upload_to_play_store_internal_app_sharing command to upload the apk/aab
I am trying to implement the Google Places Autocomplete API sometimes I am able to get location list but sometimes I get "can't load search results" message. Can someone pease help me with the issue.
This issue have a few possible reasons:
No billing account associated to the project
If you are still using the old Places
SDK
If you reach your quota limit(e.g. self imposed cap
usage)
If your app is not properly
restricted
If any of the above doesn't fix your issue, it would be best to reach out to the support team of the Google Maps Platform as this error commonly has something to do with your configuration in the GCP console wherein only the support team of Google Maps Platform can assist you.
Hope this helps.
i already added the billing service also then get the same error then i added the api key in gradle file and then its works for me
Added your api RNGP_ANDRIOD_API_KEY=***** in gradle.properties
If any of the above still doesnt work, and if you happen to be using an emulator to run the app, try uninstalling the app, then re-installing it when you run the program in android studios.
Background info:
I happened to encounter this issue on my emulator despite doing everything mentioned above, but when I tried downloading the app onto my phone, I found it working there so I tried uninstalling the app on my emulator and it worked after.
I am using NearBy 2.0 API version 'com.google.android.gms:play-services-nearby:12.0.1' with android things 'com.google.android.things:androidthings:1.0' to create a smart home app, but previously upto 8th may it was working fine with the build downloaded from android things console, but from yesterday it is throwing com.google.android.gms.common.api.ApiException:8007 STATUS_BLUETOOTH_ERROR. when I am starting advertisement or discovery whichever maybe. But if I use the previous build (image with apk) of 8th may it is working fine. I tried with that old apk also like new os image with old apk, found not working. In logcat I found it is unable to start listening for incoming connections.
I searched SO and google a lot but no solution worked. Even followed this Error codes in Nearby Connections 2.0 but no luck. I am using Raspberry PI 3 model B.
Help!!
Android Things 1 comes bundled with Google Play Services 12.5.20. Try updating your dependencies and see if anything changes.
Finally I got it working , actually when I was configuring the hardware during the build preparation in android things console there I used Starter Kit configuration which by default configured UART as UART0 (disables Bluetooth) , hence the exception it was throwing com.google.android.gms.common.api.ApiException:8007 STATUS_BLUETOOTH_ERROR. during init of nearby where I was starting advertisement.
So the fix is change the configuration of UART to MINIUART in android things console and create the build.
This person has a similar issue to me Firebase for android not working in my test device suddenly but it was never answered, and the people in the comments seem to have a similar issue.
I can access (and update) values in my firebase using nodejs but when I try to do it from android, there are no failures in logcat or anything, it just does not update anything in the database.
I checked the database reference and it's exactly the same as in my nodejs script, and my security settings are read: true, write: true... It just doesn't make sense why it's not working anymore. The exact same code was working fine yesterday.
Does anyone know what could be going on?
After spending HOURS on this myself - the revolutionary solution is to quit the emulator and reopen it again / restart your device.
In my case, it would work on an emulator but not on a real device. It turns out I had to reset my WiFi router. This answer helped me: Firebase database listeners don't work on android with wifi
I had the exact same issue. Looked almost all the blogs,even contacted firebase support as well but couldn't find the solution. Finally here is the solution.
Just update your existing google-services.json from Firebase->Your project's Project Settings.
Rebuild the app and try it out!
Remove firebase from your android project and then again connect it Properly!
Delete the project from firebase.com, it will delete the API keys from google cloud console.
Delete the implementations from build.gradle just remove each line containing firebase word.
Remove the GoogleServices.json file.
Remove the plugins from the build.gradle at the beginning.
Now invalidate caches and restart.
clean the project.
And with a fresh start connect the app with firebase and then things should work properly.
Mine was not working because I mistakenly deleted the keys from google cloud and then things became worse. I was unable to undo the step cause I am not an experienced developer.
CHECK THIS ANSWER ALSO - Firebase credentials API deleted mistakenly not working after creating api manually