I know that there have been a few posts linked to this issue, but I was unable to find one that solves my issue. Many posts have mentioned needing 3 keys in order to use Google login for Firebase, but for the past year, my personal project has done fine with just 1 key, the debug key. I have never generated an APK nor published to Google Play, hence I do not think that the other keys are necessary. All I want to do is to be able to log in to the application on my emulator using a gmail account. Normal email authentication works, as well as other firebase database and storage services, so I'm especially confused.
A couple weeks ago I renamed many of the directories in the project. I'm not sure if it is a coincidence or not, but checking the git logs, the authentication works before the renaming but does not after the renaming. This meant that I edited the google-services.json file, which is now different from from the one that I download from the firebase console. Could this be the reason? It's several commits and hours of work behind the current head though.
I have verified my fingerprint SHA1 on the firebase console with the one on Android Studio. They are identical. I'm not sure what else I need to do. Any help would be really appreciated. Thank you
Edit: I should also add that I saw a youtube video that just deleted the firebase project and restarted. That is a true nuclear option that I do not wish to do...
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 2 years ago.
Improve this question
I recently successfully published my first flutter app connected to firebase with firebase-googleSignInAuth. I tested it several times by building apk with command line. In this case, googleSignIn just worked fine. But when I downloaded my own app from playStore after well reviewed by google, following problem occurred:
I clicked a button calling googleSignIn(connected to firebase) function, then google pop-up came up. I entered my google account which is already listed on my firebase db, and the logIn process just worked fine with the pop-up screens. At this point, the problem occurred: I entered correct google account info and the pop-up from google was gone. But NOTHING happened and the logIn screen was there again. Several more same trials with restarting, re-downloading, but all didn't worked at all.. In my code, if the auth function called user info properly, home screen comes, otherwise the logIn screen comes, which means that the googleSignIn didn't work well. So I built apk from same codebase of the aab(appbundle file) uploaded to playStore, then tested it in various android devices. Unfortunately, they all worked okay with that googleSignIn issue. It seem like the problem must be in process that publishing the appBundle to playStore.
Does anyone know how to solve this playStore problem? I'm new to publishing apps so cannot find out proper solution for this issue and so devastated after all.
Of course, flutter doctor said no issue found ]:
Clear answers so appreciated! Thank you in advance! [:
I think the problem you have is in adding a SHA-1 certificate fingerprint to the uploaded application. You can add it in the Firebase project.
First: Go to Google Play Console > Release Management > App Signing > Copy SHA-1 certificate fingerprint.
Second: Go to the Firebase project > Settings > Add fingerprint.
After applying these steps, you can try the application without
re-updating the .abb version.
SHA-1 is defined as:
It is a standard for the implementation of a 'secure hash algorithm' - a one-way cryptographic function that can be used to act as a 'signature' of a sequence of bytes. It is very unlikely that 2 different byte sequences would produce the same value (though not impossible).
You can read more with Documentation.
Inb4 its a duplicate, I know the question is, but they are all older and none seem to help with my issue. Mine seems pretty cut and dry. I have an app that I build with a set of keys and upload to my play console. I have "google signature" enabled so they sign my apps as well. I have products enabled that work when the app is downloaded from google play test track. The SAME EXACT CODE BASE, signed with the SAME EXACT SET OF KEYS I used before uploading to the Play console does not work when I build locally and push it to my device. It says "This device is not configured for transactions" or something along those lines. I'm trying to build out my purchase flows but this is really obstructing me...
Everything is set up according to other answers. Same version code, products active, test track/alpha release are both available. Hell, the purchase flow starts fine when I download the apk from the play store, just not when debugging in AS.
I don't think this is a true answer, or maybe it IS and my symptoms are a bug on googles part, however I seem to have resolved my issue. I'll confirm my answer if this continues to work throughout the day.
For anyone else having a similar issue to me, delete all storage/cache for the app on your phone, then delete the app (NOT USING THE PLAY STORE). Now, install the app from your internal test/alpha track (FROM THE PLAY STORE). Run the app, test the purchase. If it works, close the app and delete all of its storage/cache and the delete the app (NOT USING THE PLAY STORE). At this point you should be able to upload test builds to your devices using Android Studio and have inApp transactions work. Idk why or how this works but YOLO, If it continues to work ill come back and verify this answer. Hopefully this is something google can get streamlined, or maybe I'm doing something wrong and just don't know it. Feel free to answer and I can change my correct answer.
I am working on client project. I submitted the android app on play store from my account. It was showing on Play store. Than according to requirement i have to publish the app from client play console account. I removed app from my account and published the same app with different package name. Than it shows app rejected because of some family policy violation. I fixed this and resubmit the app. Now it taking a lot of time in reviewing the app.
I have tried to resubmit the app after editing the policies required by google.
I want to know how much time google will take to republish my app after reviewing it again.
Or How i can connect from google with any #support email.
It usually they review my apps within few hours... but... I feel there's something wrong inside Google and one of many emails I had from their support told me it's because there's a new review process for apps on the Family program. Well I will tell a little bit about my journey may give you some idea why you are having this problem.
We experienced this problem with 2 apps:
First App: I received a message saying that my update was rejected because of the violation on the Family program alleging that it was crashing or giving an error (pretty generic message without any detail at all), I enter in contact on the support form and they send an email asking for me to read the terms and to update my APK number and submit again, I read the terms, I already had complied with everything so I replied saying that, we already comply with everyhting and we tested the APK and OBB installation and game play, all good, please send more details, they replied copying and pasting the same message, I once more insisted and asked for them to explain the problem, they replied asking for update my APK version and submit again, I said this will solve no crashes, please explain what is the problem and the support called Sara highlighted in the message asking to update the APK version, kind of talking with a machine that do not responded what I asked, but I updated my APK version, submitted again and... Worked. Why? For some reason they will not explain, my guess is they just marked my APK as dirty as an attempt to remove apps that the developers don't update, there's no other logical thing I can think off.
Second App: This one I didn't had a happy end as the previous one, I tried the technique of updating the APK version 6 times, none worked, I asked help on the form (many times), they just copy and paste the message about read the Terms, I started to insist for some details, provided them with many proves that my APK+OBB files sent to Google Play are working fine, and asked for any clue about this "problem", like a device model and Android Version that they experienced it (isn't the minimum they suppose to provide us?) but after requesting this many times, for the first time the support guy called Arthur didn't copied and pasted and finally wrote an email, his answer was:
Hi Developer,
Thanks again for contacting the Google Play Team.
As much as I'd like to help, due to policy, I’m not able to provide any more information or a better answer to your question. In our previous email, I made sure to include all the information available to me.
If you have a different question about Google Play policies, please let me know.
Regards,
Arthur
The Google Play Team
It means, he has no information at all about what is the problem, I've trying to solve this for 2 months, our flagship game is threatened of been removed from the store and they can't even explain why, the support team can just copy and paste a generic message without any understanding of our problem and we have no other channel to ask for help.
I'm really disappointed with Google for such poor support for developers.
Hope you can solve your problem updating your APK and submitting again, otherwise you can enter on the same loop as me.
Good luck!
I'm trying to use the Firebase Storage for images in my app. What happened was I wanted to change the name of my app as I've changed my mind on what the name will be, and so respectfully I updated the Firebase Console Project.
Corresponding name spaces were updated. After the rename of the app project I wasn't able to download the google.json file anymore. Even after deleting the entire project, and starting from scratch the google.json just wouldn't download kept saying there was a problem with the server.
There is another question with this inquiry, but it didn't have a single issue after upgrading to the new Firebase, and the question that is regarding this is specifically about having been upgraded . It took some learning, and there still isn't as much documentation as I'd like. For example, the FirebaseUI (ListAdapter) and such. Would solve a lot of my current issues in regards to handling data being moved, updated, deleted, etc.
Is there any way to know if this specific bug issue has been reported? Is it a known issue, and is there a possible timeline? I plan to scale the app once I launch and am afraid to do so as once I do. I will be upgrading the plan to the $25 plan for better simultaneous connections.
Any help would be graciously appreciated.
UPDATE
Since a few days ago I was able to download the google.json file. That is great! However, the issue still remains. I cannot use the Storage, and it's giving the same error as the attached image.
Also, I have submitted a ticket with Firebase Support. Communicating with Firebase Support currently via email. Will post updates as I have them.
Recently I try to implement a leaderboard by Google Play Game Service.
And first I import that sample project TypeANumber. I follow the way here https://developers.google.com/games/services/android/quickstart step by step.
I used the keytool to generated the SHA1 of keystore, and use this SHA1 to verify the app.
Then I sign the app by the keystore.
When I run the sample and try to sign in. I got the error "Google Play Game Services - unable to sign in".
Then I double check all my steps and try again. Still got this error.
I searched this problem on google, and I find this man got the same problem with me
Google Play Game Services - unable to sign in
All the situation is the same. And he got the solution.
I follow his solution delete my app client ID on Google APIs Console, unlinked my app and relinked it with the proper Certificate Fingerprint.
All this work done, I still got the same error.
Did I miss something? Any body got the same problem like this ?
Or maybe I should create an app with the same package name of the sample project and upload the apk ?
Or maybe Google Play Game Service doesn't work at China ?
I have encountered similar issues and I note that this page was updated on 30th May 2013 which
may help you, or me, or maybe even both of us !
https://developers.google.com/games/services/android/troubleshooting
Update: I worked my way through this and eventually realised that I had two different app_id strings in my project - one for the Facebook API and one for Google play Game Services! The two strings were stored in different files so my error was hard to find. Once I renamed one everything worked fine. One problem that I have encountered is that I am unable to test with the id that I used to define the Game in the developer console. Other people have mentioned this elsewhere on SO but no harm mentioning it again.