Deleted OAUTH client for production flutter app - flutter

I am using flutter for developing an application with google_sign_in package. We had some unnecesary clients in our google cloud console. I accidentaly deleted the one used for the production app. I created a new one with the same SHA-1 fingerprint as the old one, but the oauth client gives the following error.
PlatformException(sign_in_failed, com.google.android.gms.common.api.ApiException: 10: , null, null)
If I generate a new keystore file and add it to the cloud console, the login works. But I can't upload the application to the play store because the keystore file has changed.
We should roll out an update in the next few days, what are my options?

Related

Is there anything wrong with Unity GPGS Production Setting?

Currently, my Unity Android app that I uploaded as a production on Google Play has a big problem.
We started Google As advertisement and checked the inflow of users (installation of 1,597),
However, there are only 67 users who have actually accessed it...
I downloaded my app that I uploaded to Google Play directly and logged in with my Google account, so there was no problem, and I asked my friend to download and run the app, so there was no problem logging in.
The predictable problem is that due to the number of concurrent users, many users are unable to access when starting the advertisement, or something seems to be wrong with my GPGS setting.
Please check the possible problems and the image of my GPGS setup.
**Setting **
Unity Ver : 2021.3.8f1
GPGS Plugin : 0.10.14
State
Upload Google Console Production
Google Console -> Play Games Services -> Setup And Management -> Configuration -> Publish Complete
Create 3 Google Cloud Platform OAuth Clients
-> Upload key, app signature key, server
1. Suspected Problem 1
If the AndroidManifest.xml Package Name is different from the package name of the Google Console, can the Production user not access it?
Unity -> PlaySetting -> Identification -> Package Name is entered as the package name of the Google Console, but AndroidManifest.xml Package Name is marked as package="com.google.example.games.mainlibproj" and modified it directly to the package name of the Google Console, but it was restored again.
enter image description here
enter image description here
(If it is a problem and you need to check the Unity error list, you can attach it later)
2. Suspected Problem 2
Can't the user access because Unity's keystore certificate is set to upload authentication signature, not app authentication signature?
enter image description here
3. If you have any other problems, please give us your opinion.

Implementing google login flutter gives 12500 error

I implemented google login in flutter without using firebase in flutter (google cloud console). It was working in apk then later I needed push notification service for which I used firebase (fcm token and all) then I released the app to playstore but google login does not work. I keep getting apiexception error. Has anybody faced this issue? if yes any help would be highly appreciated.
I do not have a specific answer to your problem but I have also faced this problem once, I accidentally resolved it though.
But Error 12500 is a general error code that may occur when attempting to use the Google Sign-In feature and is caused by a few potensial issues:
An issue with the SHA-1 fingerprint of your app's signing
certificate: To use Google Sign-In, you need to configure your app's
SHA-1 fingerprint and package name in the Firebase console. Make
sure that the fingerprint and package name you have configured in
the Firebase console match the ones you are using to sign your app.
An issue with the Google Services configuration file: Make sure you
have properly added the Google Services configuration file to your
app.
An issue with the Google Play Services library: Make sure you have
the latest version of the Google Play Services library installed in
your app.
An issue with the device or emulator you are using: Make sure you
are testing on a device or emulator that has Google Play Services
installed and is up to date.
Possible fixes to try/check:
Double-check the SHA-1 fingerprint and package name: Make sure that
the SHA-1 fingerprint and package name you have configured in the
Firebase console match the ones you are using to sign your app.
Make sure you have added the Google Services configuration file: The
Google Services configuration file is required for your app to
communicate with Google services, including Google Sign-In. Make
sure you have properly added this file to your app.
Update the Google Play Services library: Make sure you have the
latest version of the Google Play Services library installed in your
app. You can check for updates by going to the "SDK Manager" in
Android Studio.
Test on a device or emulator with Google Play Services installed:
Make sure you are testing on a device or emulator that has Google
Play Services installed and is up to date.
I hope this helps! I will quickly search if I can find any other solution.

how to change firebase account in a flutter project?

I created a flutter project with my personal firebase, but now the client has already created his firebase, how do I change the account in a project, I've searched the documentation but without success?
Unfortunately there is no easy way to switch.
The information you configured when you first created flutter project on firebase, it has be configured again with clients Firebase.
For example -> replace old GoogleService-info.plist, android package name and iOS bundleID with the new one.

Ionic release not installing after implementing facebook login

I have install facebook login plugin to my ionic application and generated hash and added to facebook developer console. I have generated debug application and it works well by installing.
But when i generate release apk it is not even installing after uploaded to google drive as it is installing when i generate debug app.
I have not generated debug keystore from the start of my app, i just has generate release keystore only.

Uploading Application .apk to Google Play with different Eclipse

In the previous Eclipse that I used, my keyhash has been created and edited on developers.facebook. At the moment I am using a different Eclipse and have some doubts while creating new keystore and new apk.
My questions are
1-) Do I have to create new keyhash for my new Eclipse for developers.facebook?
(before it was required when I tried to login to application with facebook, but on my second eclipse I was not warned by the device)
2-) Will I lose my users on google play if my keystore package and apk names are different.
Note:
My keystore password is same. Thank you its so important for me.
android:versionCode has been increased