Develop Reference

Firebase unable to process request due to missing initial state

I am trying to use phone auth from firebase and I get this error now.
Unable to process request due to missing initial state. This may happen if browser session storage is inaccessible or accidentally cleared.
This was working a week ago and no longer works.

I have solved this by registering my app with SafetyNet with SHA2. To do this follow these steps:
Get your SHA2. If you don't know how to get this, follow this tutorial:
https://www.youtube.com/watch?v=kLaNnuoqnmA
Note. This youtube link is for SHA1 but you will notice that SHA2 will be shown here if you pay attention.
Go to your Firebase Console then, go to Project Settings > App Check. You will notice your app is "Unregistered." click this to register your app.
Enter the SHA2 you copied and Accept some terms below then click Save. you will notice the "Registered" with green check icon.
Btw, this error happens on one of my devices but not on another. I also searched through this error and no one has solved this including this page. This happens in my phone authentication using firebase when getting an OTP as I send my phone number. The app tries to redirect you to a browser for Recaptcha for verification if you don't have SafetyNet. Thus, having no SafetyNet will cause your app to always be redirected for Recaptcha which sometimes causes an error. Thus, to solve this, register your app with Safety Net. to understand this, read this documentation.
https://firebase.google.com/docs/auth/android/phone-auth?authuser=0
Focus on 2. Enable App Verification and you will notice that recaptcha is just an alternative for SafetyNet.

It had on the Ionic/Angular/Capacitor app too. i.e. Android and Chrome. Firebase Auth with Microsoft Login.
So I have cleared all the chrome browser data on the Android device and then no issues. i.e. working fine now.
More workarounds: https://github.com/firebase/firebase-js-sdk/issues/4256

I experienced the issue with an iphone web app. I went into Settings -> Safari and disabled 'Prevent Cross-Site Tracking'.

Google OAuth sign-in stuck loading consent screen

My app uses the Google Drive API to back up user files. I wanted to test my app sign-in from scratch so I manually revoked the app from my Google account settings but when I go to sign in again, I'm stuck loading the consent screen (see below) after choosing my Google account.
This is what I have...
Publishing status is "Testing", user type is "External", and I've added/using the right test users
Registered both my debug and production keys under OAuth 2.0 Client IDs
Scopes are only "./auth/drive.appdata" and "./auth/drive.file"
Domain is verified, provided organization website, support email, privacy policy link, and custom app icon
This is what I've tried...
Reinstalling the app and clearing data
Waiting about 24 hours
Removing the Google account from the device and signing in again
Deleting and reuploading my debug SHA-1 key
Disabling and reenabling the entire Google Drive API
Using a different Google account that has never been used with my app before (makes me think it's something on Google's end)
Using different test devices (emulator + physical devices)
Checking out old code branch from known-good time (in other words, sign-in code is the same)
I emphasize again that this sign-in and OAuth flow was working before (albeit showing the consent screen for "unverified" apps since it's still under development). I have not changed any scopes nor reconfigured the OAuth consent screen.
Does anyone have advice on other things to try here? Given that this was working before, I'm not sure what else I can change from my Google APIs dashboard.
I understand that my question is very similar to one asked before, however in that case apparently using a different account ended up working – that is not the case for me.

Mine was the same case. It used to work fine, but then after some months Google sign in Screen asked verification, and then after some days this loading stuck issue appeared.
But the issue was of Goole Drive Scopes if you don't want to go for verification and your use case is simple then use recommended scopes as mentioned here https://developers.google.com/drive/api/v2/about-auth
I just wanted listing, getting and creating of files, the below scopes did the work for me
GoogleSignin.configure({
scopes: [
'https://www.googleapis.com/auth/drive.appdata',
'https://www.googleapis.com/auth/drive.file',
],
...
...
});
taken the create file scope from here https://developers.google.com/drive/api/v3/reference/files/create

I had the opposite problem of most of you: my consent screen worked fine in testing mode but got the infinite loading bar in production. It turned out I was using the wrong Google Photos scope in my app code. I was only requesting https://www.googleapis.com/auth/photoslibrary.readonly in Google Cloud Console, but in my app I was using https://www.googleapis.com/auth/photoslibrary. I'm still not sure why I was allowed to use a broader scope in testing but not in production.

Had a similar situation when my app was rejected for using 'YouTube' in the description after being on the Play Store for 4 years...[but anyway]
After dinking with it for a long time and creating new credentials all kinds of stuff
I went to:
google account
revoked access for the app in question
in the dev console: move the app back to testing [make sure you have testing users on your list]
uninstall the App
install the app
after I picked the account, I got the same blank consent screen with a twirling progress dialog, but I also got an email; once I confirmed it was me through the email the progress bar went away and I got the oauth dialog as expected, when I clicked allow, everything worked. Back when I originally built the App before it was rejected, I don't remember the email confirmation being required, but I could be wrong. I swear I had tried this a dozen times. I wonder if Google does something on its end...

I eventually got it working after I changed my consent screen to production mode instead of testing. The issue on Google's end (see comments) seems to have been closed with "Won't fix (inactionable)".
Update: There appears to be different causes for being stuck at the OAuth screen. In my particular case, it turned out to be a Google-side issue that I believe they later may have fixed. Other answers here may be equally helpful but I've accepted my own answer because that was specifically the conclusion to my own problem.

Can't add social login with Google on Android - but on iOS it's working

I'm trying to add support to social login with Google on my application using the package google_sign_in.
I got to add support of that on iOS, and it's working. But on Google, for some unknown reason, it can't work anymore.
Few days ago it was working, but now it just start the following loading, and then shows the error Couldn't sign in:
On OAuth consent screen, since I updated some informations on my application, I needed to request again the authorization, but it says that the previous consent is still in use... but I don't know if would be the root of the problem and I really need to wait 4~6 weeks to work again on Android.

The problem was fixed. It was being caused by a wrong jks of Firebase.

Google EndPoint not getting called when request has google plus profile url as parameter

My app uses Google App Engine as backend and it provides google plus & facebook login option to user.
One of the endpoint Api takes user profile picture url as input parameter and tries to store it in the user profile table. My endpoint Api was not getting called successfully when user choose the option of google plus as login,
I have narrowed down the issue to find out that it only happens during google plus login scenario and from the backend logs I see the issue is only because of below parameter which is profile photo url.
https:%2F%2Flh3.googleusercontent.com%2F-xPc6TIzQiFA%2FAAAAAAAAAAI%2FAAAAAAAAAeU%2FUIIpz-4G1dQ%2Fphoto.jpg%3Fsz=400
Backend Request from logs(Data changed for privacy reasons).
/_ah/api/registrationAPI/v2/XXXXXX/Rahul%20Purswani/rahulfhp#gmail.com/https:%2F%2Flh3.googleusercontent.com%2F-xPc6TIzQiFA%2FAAAAAAAAAAI%2FAAAAAAAAAeU%2FUIIpz-4G1dQ%2Fphoto.jpg%3Fsz=400/XXX/YYY/VVV, returning NOBODY to imply authentication is in progress.
My Api Class Declaration :
#Api(name="registrationAPI",
version="v2",
namespace=#ApiNamespace(ownerDomain="backend.XXX.XXX.YY",ownerName="backend.XXX.XXX.YY",packagePath=""))
public class PlayerRegistrationEndPoint {
}
And to my surprise this only happens when I test the Api on local development server through real device. If I deploy my api all works fine, I have spent almost the day to narrow it down, If you have any clue about it that will be really appreciable.

Are you accidentally logging the bytes of your pictures using logging.info(), logging.error(), print, etc? Logging bytes to either the logger or standard out can make the dev instances (or even production instance) go into zombie mode.
This has happened to me many times. Check all logs to make sure you aren't trying to log something that isn't a basic variable type.

I was getting this issue since we migrated our code base from Eclipse to Android Studio, during this migration our app-engine sdk version got changed from 1.9.22 to 1.9.18.
Looking back and doing comparative analysis with why it used to work with eclipse, I tried using 1.9.22 app-engine sdk here and issue got resolved, the zombie behavior is no more and even in development environment everything is stable now.
I also checked & removed all the loggers and out statements, though the issue was not fixed with trying that alone.
Thanks for even letting me know that it can also go wrong in future during development environment testing.

Linking Play Developer Console to Google Wallet Error

I've a major issue with linking my Play Developer Console to Google Wallet. I've already search the Google Help for any solution and didn't find one. The problem is, that Error message appears after hitting “Set up a merchant account now” button in my Google Play Android Developer Console (Settings/Account Details). After that another screen pops out with an error:
Oops! An error occurred while processing your request.
Regardless of any steps I've done such as changing to a different browser(Firefox to Chrome and back), clearing cache&cookies and so on... nothing is working.
Any ideas?

Any resolution yet?
I just encountered the same issue. Also no followup from google teams.
A possible solution I am looking into is to use an alternative payment system such as http://www.zooz.com/

I have the same problem a few days ago. After exchanging several emails with the service, they didn't know to tell me what happened, only they made me waste time. Then I started to fill the form on the Wallet account to avoid having to write every time I tried to link the accounts, and in this form itself is run the Javascript and I notice that my address could not be longer than 64 characters... I wrote a short version and I got my accounts linked.
In short, if you can not link your Google Play and Google Wallet accounts, check the size of your inputs, Javascript alerts dont work fine.
BTW: Outside USA could also be the fault of the VAT-ID, try to leave it empty.