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
Related
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?
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.
I have completed an application that works fine in development env, both on android emulator and android phone.
I created a keystore, added INTERNET_PERMISSION to my manifest and followed the guide to release pretty much perfectly.
However, when I download the release app from the play store (it is in internal testing), the login API (and presumably the other APIs) do not work and infinitely load.
What did I miss?
The IOS Application is working perfectly in Testflight.
Assuming that you are using firebase.
After deployment to playstore.
Go to Play Console → Open App → Setup (Left panel) → App Integrity
you should be able to see something like this.
add the SHA-1 and SHA-256 fingerprint to the firebase project in firebase console and it should work after that.
Open Firebase Console → Open Project → Project Settings → General, scroll to very last and add these certificates.
UPDATE:
You need to get the new google-services.json from firebase, add it to your app, make new build and re-deploy to playstore with a new version for this to work.
When I install my proyect using usb, the map works fine but when I want export my proyect (.apk) and install the app, the map doesn't work just show blank display. Any advice.
UPDATE: I have my proyect and google play services library in my dropbox and the debug.keystore in the root c:\Users\my_user.android\debug.keystore
I have tried to do this but without success: Google Maps API V2 blank map after installation on real device
You have to update your SHA key in google console project.
You just replace exported SHA with old SHA key.
Exported SHA get like.
1) Export your project with create key store at that time you get exported SHA .
That was the solution, I needed the release key. Here is how to do that. Displaying the release certificate fingerprint
After implementing maps layout activity and manifest and other required files , the app should be build with the keystore provided in android sdk itself instead of our own keystore. keystore path - C/user/{username}/.android/debug.keystore with alias as "androiddebugkey" and password as "android"
I want to use my custom keystore in this project because I intend to host the application in PlayStore and keep it updated. Without the keystore will be tricky.
Details: In the settings cordova, I not marked the "Signed" box and I exported the app and tried signing it using javasign. At the command prompt went well but the app does not install on any of the devices I tested.
The APK created by the Intel XDK is created using standard Cordova CLI. So the techniques you would use to sign that APK are no different than what you would use with any other Cordova (or PhoneGap) app or an APK built using Eclipse or any other tools.
See these links for some useful information:
-- http://developer.android.com/tools/publishing/app-signing.html
-- https://www.scirra.com/tutorials/861/how-to-sign-and-align-your-android-app-apk