I'm using SHA1 debugging key in firebase for debugging my application, but I want to release my app in the play store where I'm providing Google authentication in my application.
What can I do for release mode where do I get SHA1 release mode certificate and what can I do with that?
Is it necessary to download the json file again? How can I do that?
I had the same problem and found this enter link description here
Basiclly what he did, and for me works fine, is one you upload the app to google play:
Go to Release Management
Select App Signing
Use the SHA1 that you see there in FireBase
Related
I have implemented the Push Provisioning API using Google Tap and pay client.
While querying linking token I am facing the below exception.
W/System.err: com.google.android.gms.common.api.ApiException: 15009: Calling package not verified
I have tried to create signed apk and install, but still same issue
Anybody help me out to unblock me?
that error occurs when you don't have access to push provisioning API.
You can see it on the troubleshooting page:
https://developers.google.com/pay/issuers/apis/push-provisioning/android/support/troubleshooting?authuser=1
To solve this you need to ask access for Push Provisioning API. Google has to identify your application as well as its version(production, development, debug). Versions as you know are differentiated by the key that signs them. Generate the correct version of your app gets its SHA 256 fingerprint and provide it in the aforementioned form.
Here are the instructions:
https://developers.google.com/pay/issuers/apis/push-provisioning/android/allowlist?authuser=1
Key used to sing your app on the Play Store maybe different than the one you use locally to generate signed apps. Also Debug versions take the default key from .android directory(you can find other stack overflow posts that provide information about debug keys and their credentials.)
I am using android studio version 4.2 beta 3 and while I am using the GUI to push/fetch the studio prompts to login on github while I have already set an account.
The strange this is that I can use git on terminal but not on GUI.
I select the first option and my browser navigates me to a website that says to authorize in Github, I press the button, login on Github and then I get the following localhost page which needs some unknown credentials.
Do you have any ideas on how to fix this issue?
Thanks
This actually turns out to be an Android Studio bug.
See e.g. this and this reports
In the corresponding IntelliJ IDEA version it is working fine.
Log in using a token instead, as a workaround.
Unfortunately the issue still persists in android studios latest release but your workaround of Token works.
you have to Generate a new SSH key and adding it to the ssh-agent ,
you can find it there
My Github account is using the Single Sign-On from my organisation, so what worked for me was to go into Github settings -> SSH and GPG keys and then clicked on the button Configure SSO on my SSH key. Then click on "Authorize" for your organization.
Here's more details on how to do it https://docs.github.com/en/enterprise-cloud#latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on
This works when you get the following error while checking your project out
Clone failed
ERROR: The `----' organization has enabled or enforced SAML SSO. To access
this repository, you must use the HTTPS remote with a personal access token
or SSH with an SSH key and passphrase
that has been authorized for this organization. Visit
https://docs.github.com/articles/authenticating-to-a-github-organization-with-saml-single-sign-on/ for more information.
Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
The app bundle was generated by the first PC (Ubuntu 18.04) using keystore and its password. Google Play accepted app bundle and application was updated successfully.
After that same process was repeated in another PC (same project, same keystore, same password) and successfully generated app bundle. But Google Play did not accept it and showing error:
App bundle was signed with wrong key. Choose appropriate key: SHA1: C9:AF....
I tried different ways to solve this problem:
Tried to create app bundle on Windows and MacOS machine. Could not try on Linux machine because there are no Linux machine available
Besides the app bundle trying to create the apk which was generated successfully, but when uploading Google Play showed error: signature is invalid
Developer who owns Linux machine is leaving project and we need to generate app bundle in another machine.
What is the reason for this problem if app bundle is created by same keystore and password? How can I solve this problem?
I'm pretty sure even though you think it is being signed with the same keystore, you have made a mistake somewhere. You can check this for yourself though. App Bundles are just signed using the same scheme as jarsigner. So you can print them using keytool.
keytool -list -printcert -jarfile mybundle
If the values are the same for the bundles produced on both PCs then they are signed with the same key in the same keystore. Otherwise you are doing something wrong. Maybe using a release key on one, and a debug key on another, or the keystore has two different keys with different names. Or maybe you think you are using the keystore when you aren't.
Google play accept the apk generated by same keystore file. So please check you have made some mistake. Use the previous keystore and compare it with the current one to check and verify the SHA! and SHA256 Signature
if upload an Application on play-store with one Keystore you don't need to create another keystore for the same project, just use the same keystore for your next version uploading.
NOTE: Google not allow to create multiple keystore for same project.
Remember the selection of signature of version what you selected. this must be the same for your next release.
I'm setting up a new app and I need that to authenticate with firebase. I have tried a lot of different codes to get SHA1 key but I am unable to do so. Please help me.
Checkout the image please
You can easily get SHA1 for your app using Signing Reports option from your IDE. Please check image below.
Please note:
You will have to mention your keystore details and create a signing config in project settings / Gradle file. once your signing config is added, using this option you will be able to get SHA1 for signed apk as well. Otherwise there will be SHA1 for Debug config.
Result as :
I understand the need to provision apps when you are getting close to deployment; however, right now, I am just trying to play with some sample code. Specifically, the GKRocket demo that ships with iOS 4.2 SDK. I want to compile and run it; however, I get the following error:
Code Sign error: a valid provisioning profile matching the application's Identifier 'com.apple.GKRocket' could not be found
The readme.txt claims "Build the game simply by opening it with Xcode and clicking on Build and Go."
I just read the following thread
Code Sign Error When Building iPhone Application
and the following
http://developer.apple.com/ios/manage/bundles/index.action
Since the app is using the NSNotificationCenter, it leads me to believe that I need an AppID. But shouldn't the demo already be pointing to and AppID setup by Apple for the demo code?
The plist shows
Bundle identifier com.apple.${PRODUCT_NAME:rfc1034identifier}
any ideas on what I should do to compile and run this in the simulator?
Update:
I was able to get it running by code signing, but never could compile without it :(
It appears since the GKRocket Demo is using the NSNotification Center that in fact you need to sign your code. You can sign your code with your/or your team cert. Change the Project -> Project Settings -> Code Signing Identity to use your cert. Note: If you don't have your cert, and you paid the $99 dev license go through the steps here.
Then open the plist file and change the bundle to your domain name.
Also, to get the GKRocket Demo running, make sure you turn on Bluetooth in your network settings.
System Preferences -> Bluetooth. Turn it on and check discoverable. Then go into advanced settings
Install your app on your iPhone with a build and run. Close the debugger. Then start your app in the local iOS simulator. Now manually run your app on your phone.