How do I get past this error in the Firebase console when adding a new app? "There was an unknown error while processing the request. Try again." - firebase

I'm getting this error after I try to add a new app and click 'Register App':
"There was an unknown error while processing the request. Try again."
I've looked at these and they have the same problem but didn't have solutions that worked:
Can't create Firebase project - There was an unknown error while processing the request. Try again
GCM - Getting Error message "There was an unknown error while processing the request. Try again." when creating new project
Firebase: There was an unknown error while processing the request. Try again.
I'm not using multiple Google accounts. I've tried signing out and in again, tried changing the package name, and the Firebase status page doesn't show any outages.

I had the same problem, After a long research fond that it was been OAuth 2.0 Client Id limit. In order to resolve, I have deleted all OAuth 2.0 Client IDs from Google cloud console, then try again. It works fine for me.
Steps to remove OAuth 2.0 Client IDs :
Open 'https://console.cloud.google.com/'
Select your project from the top navbar
Select APIs & Services from Left Side panel
Select Credentials in the left panel
Go to OAuth 2.0 Client IDs
Select all unused Entries (!Carefully)
Click on delete on the top bar
Done, go to firebase console try again
It may solve your problem!!

Have you tried changing your package name? I'd same issue,that was resolved by changing package name. As Firebase saves deleted package names as well.

You might reached number of OAuth 2.0 client IDs limits. There is a limit of around 30 client IDs that can be created within a single project.

Make sure you sign out all your google accounts and sign in with the account for your specific project. I'm normally signed in to 3 or 4 accounts and ran into this error issue. Did as I mentioned and it worked.

The operation has failed (Reason: [object ProgressEvent])
I am getting the above-mentioned error while creating a new project. This got resolved by logging out and logging in again

Related

Authenticating Google Cloud Storage in R Studio

I know a similar question has been asked (link), but the response didn't work for me.
TLDR: I keep running into errors when trying to authenticate Google Cloud Storage in RStudio. I'm not sure what is going wrong and would love advice.
I have downloaded both the GCS_AUTH_FILE (created a service account with service admin privileges'--downloaded the key associated with the service account) and also downloaded GAR_CLIENT_WEB_JSON by creating a OAuth 2.0 Client ID and downloading that associated JSON file.
I've tried authenticating my Google Cloud Storage in several ways and hit different errors.
Way 1-automatic setup:
gcs_setup()
Then I select any one of the options, and get the error: Error in if (file.exists(local_file)) { : argument is of length zero And that error happens no matter which of the three options I select.
Way 2 - basic, following manual setup instructions from the package:
Sys.setenv("GCS_DEFAULT_BUCKET" = "my-default-bucket",
"GCS_AUTH_FILE" = "/fullpath/to/service-auth.json")
gcs_auth()
In this case, GCS_AUTH_FILE is the file that I mentioned at the beginning of this post, and the GCS_DEFAULT_BUCKET is the name of the bucket. When I run the first line, it seems to be working (nothing goes awry and it runs just fine), but when I run gcs_auth() I get taken to a web browser page that states:
"Authorization Error
Error 400: invalid_request
Missing required parameter: client_id"
Way 3: Following the method from the post that I linked above
This way involves manually setting the .Renviron file w/ the GCS_AUTH_FILE and GAR__CLIENT_WEB_JSON locations, and then running gar_auth(). And yet again, I get the exact same error as in Way 2.
Any ideas about what could be going wrong? Thanks for your help. I wasn't sure how to put in totally reproducible code in this case, so if there is a way I should do that, please let me know.

Artifactory Users Management not loading

I'm trying to open the Artifactory Users Management page, following the Admin->Security->Users tab.
Then I'm getting the following error:
Any idea of what might be causing it? Also, which log I can check this? Couldn't find anything yet.
The server error generally indicates there is problem fetching the user details from Artifactory. This can happen due to any of the following reasons:
when you have a high volume of users and the request is timing out.
There is a chance that you might have created a username with a
special character which is not allowed (using the REST method or some
other method)
There is an issue with the backend database
And the best place to troubleshoot is to first check the request log a good valid entry looks like below:
20200715164402|104|REQUEST|165.225.104.49|admin|GET|/ui/users|HTTP/1.1|200|0
Next check the artifactory.log file for java stack or check catalina.out under tomcat/logs directory.

Cloud Functions for Firebase sometimes have Invalid credential error

Not appear every time, but sometimes this error appears in the log:
FIREBASE WARNING: {"code":"app/invalid-credential","message":"Credential implementation provided to initializeApp() via the \"credential\" property failed to fetch a valid Google OAuth2 access token with the following error: \"read ECONNRESET\"."}
Is there any way to handle this kind of error like retry?
Or is it okay to ignore it?
Just ensure that your machine time auto sync. and not manualy,
And your XXX......json from firebase is the latest downloaded. (if you dont sure, download it again - and this file will be the newer one)
that what helped me.
I am also facing this issue. Looks like it retries and get the job done but cloud functions are taking time to process data.

MSG.exe Error 5 getting session names

I am trying to send a message through the command line using msg.exe on Windows 7. I have successfully gotten everything to work except for the Session ID. I get the error Error 5 getting session names. After searching online I found that I can edit the registry to remove this error using regedit.exe. However, on the domain I am on, I do not have permissions to edit the registry. I can only view it.
I know the individual session ID's of the users that I am trying to send a message to.
Super user hasn't really been any help... How do I prevent the error from occurring without editing the registry?
You need to log into the user, that the computer you are trying to send to is on.You will need to do is go to credential manager, and add the credentials. That error message will go away.

What does error 110 per AuthzInitializeContextFromSid signify? "While trying to retrieve the authorization groups, an error (110) occurred."

My symptoms and System.DirectoryServices.AccountManagement stack trace are exactly the same as While trying to retrieve the authorization groups, an error (5) occurred except that I get an error 110 which docs explain as ERROR_OPEN_FAILED: The system cannot open the device or file specified.
In my situation, this functionality was working one day and stopped working the next day within an ASP.NET v4 application. I am using an AD service account that I've created in order to establish a connection to AD. The service account has admin privileges to a specific OU further down in the directory.
I've narrowed the exception down to a call made to the AuthzInitializeContextFromSid native function inside the System.DirectoryServices.AccountManagement.AuthZSet constructor. It is not clear to me why this fails and since user.GetGroups works for me (per the answer given in the other SO link), I'll put my research on hold for now.
Does anyone else have any thoughts on what might be occurring?
Error 5 usually means you are having an ERROR_ACCESS_DENIED win32 error. That can happen if you're accessing a downlevel API that can only be queried with administrative rights or if the object you are accessing has ACLs that deny access from the process token your program is running at.
In simple words: try running your app elevated. If it works, you had insufficient access rights when running without elevation.

Resources