Android Studio App Quality Insights problem - android

I've updated my Android Studio to the latest version ElectricEel. Everything is working fine, except the App Quality Insights feature(I've updated the Studio because of this :) )
First, my Firebase plugins were disabled and the App Quality Insights window was not available at all. I've fixed this issue as described here.
Now I have the ability to launch the feature. But when the window is loaded I'm getting an error:
400 Bad Request { "error" : "invalid_grant", "error_description" : "Bad Request" }
I've checked the Firebase plugins and signed in to Android Studio. Restarted and Invalidated. Nothing helped.
NOTE: My colleagues on the same project don't have this issue.
Any hints about this?

The fix was in three steps:
Sign out from your account in Android Studio;
Restart the Android Studio;
Sign in again.
Everything should work. Also, if after sign in, you are not seeing your Google account image in the top right corner, u maybe need to re-login again.
Thanks [ArpitPatel] for a hint.

Related

Fixed - Android emulator: Auth0 login not working

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.

Firebase doesn't work on Android Studio Emulator

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.

Google Places Autocomplete Can't load search results

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.

How to republish video with new opentok sdk

I use the latest opentok Android SDK to development an application. My purpose is to provide a button to let user can publish / unpublish camera. It works to unpublish the camera using publisher.setPublishVideo(false); , but it doesn't work to republish when I use publisher.setPublishVideo(true);.
And I also try to use publisher.destroy() to delete the publish and recreate the publisher and then publish it, however since publisher.destroy has been called, either publisher and subscriber's video all disappear. It's very weird.
Am I using the wrong way or could anyone give me a hint?
OpenTok's Android SDK is still in beta so its has errors here and there. You have caught an error, and this error has been reported to OpenTok. Will update when this error has been resolved.
edit- This bug will be fixed in Android 1.0.1

Getting an error when uploading the apk to the market

" An unexpected error occurred. Please try again later. " is the error that I am getting when
I try uploading my signed apk..
Once I was done with my app, I used Export signed application tool to generate the key.
Why am I getting this error?
I found that just SIGNING OUT and back int fixed the issue for me. Using Firefox.
Try to use a different browser, or just wait.
This can help: http://www.google.com/support/forum/p/Android+Market/thread?tid=7fff4999197c33c7&hl=en
Just log out . Log in again. And yep now it works :) . If not still working clear history and then try again logging in it will surely do. However google should look on to this issue
I just experienced the same problem using FireFox, so I just switch to IE and it worked fine ...
I logged out and then logged in again. The new version is listed but a couple more steps involved. Deactivate the currently published version and click the "Publish Now" button.
They need to fix this. It is not intuitive by any stretch of the imagination.
I just had this issue, and solved it by:
Saving the apk as draft (instead of publishing it).
Deactivating the currently published version.
Publishing the draft apk.
Signing out and back in again didn't help.
Changing the browser (IE/Opera) and re login didn;t work. So I logged out, remove all signed in gmail accounts from the browser(Chrome) and then logged in. It worked.
I just spent hours trying to upload and publish a new version of my app using Firefox on the Google Developer site. Eventually I too found that just signing out and back in solved the problem.

Categories

Resources