I read many similar content but I couldn't find a solution.
I am a flutter developer, yesterday i signed an android application and sent it to google play.
I cannot find the key file I created or I am not sure if its name is the key.
I created it yesterday on this mac computer , but today there is no such file. I only have a file named 'private_key.pepk' on my desktop.
Can I find out where the path I chose when signing for the first time from my Android project? i need your help
Android developer that hasn't signed a Flutter app yet, but in build.gradle you should have something like this:
signingConfigs {
release {
storeFile file("EITHER A PATH OR RELATIVE PATH")
storePassword sPassword
keyAlias kAlias
keyPassword kPassword
}
}
Related
I made this Android app that fetches some data using AI Platform Training & Prediction API from Google Cloud Platform. For this app to work it needs to be approved by GCP using SHA-1 Fingerprint certificate. I am making this app as an assessment for module Im taking at the university, so, when the teacher will open my Android Studio project it will have a different SHA-1, so the app will not fetch the data...
Any Ideas how I might be able to maybe set a permanent SHA-1 key for my project, so when the teacher will open the project, Android Studio will not generate a new one?
Thank you!
The SHA-1 is based on the app signature. Since this is for a project I suggest you do the following (never do this in a production app).
Create a new signing key (Build -> Generate Signed Apk -> APK ->
Create New)
Move the signing key to your project's folder
Add this to your app.gradle
android {
signingConfigs {
debug{
storeFile file("your_key.keystore")
storePassword 'password'
keyAlias 'alias'
keyPassword 'password'
}
release {
storeFile file("your_key.keystore")
storePassword 'password'
keyAlias 'alias'
keyPassword 'password'
}
}
}
EDIT: Forgot to mention, run the signingReport gradle task after you do this to get your new SHA-1 that you have to add to your project.
after creating the .keystore file and running the report I get the new SHA-1 key, but the build fails. I get this:
Entry name 'play-services-ads-identifier.properties' collided
As Android debug builds get reinstalled when the same phone is connected to different MacBooks, is there any way for all development machines (MacBooks) to share the same debug certificate? It will help to avoid reinstallation on development devices.
Easiest thing to do this would be to check the debug keystore into your project and then reference it in build.gradle like so:
signingConfigs {
debug {
storeFile file('../keystore/debug.keystore')
storePassword "android"
keyAlias "androiddebugkey"
keyPassword "android"
}
release {
// ...
}
}
I think that's possible. Android Studio automatically creates the debug keystore and certificate the first time you run or debug a project in Android Studio.
Simply go to :
~/.android/ folder on OS X and Linux
C:\Documents and Settings\.android\ on Windows XP
C:\Users\.android\ on Windows Vista and Windows 7, 8, and 10
on one of your development machine and find your debug.keystore file. Copy and paste the file on the other machines at the same location.
Hope it will work!
Yes you can.
To do that, just share the certificate file located at ~.android/debug.keystore with your teammates.
You can create your own keystore for debug builds too. On Mac, this is usually found at ~/.android folder. To create Keystore, you may do following:
Create a .properties file with your project name(say, projectname.properties) file and store it somewhere in your project root or elsewhere.
Add following entries.
keystore=<path>\\filename.keystore
keystore.password=<password>
Now we need connect projectname.properties to our project. Open gradle.properties and add an entry.
projectname.properties=<path to .properties file>
We can access this properties now in gradle.build file.
You can check now if a .properties file is available.
if(project.hasProperty("yourprojectname.properties")
&& new File(project.property("yourprojectname.properties")).exists()) {
Properties propObj = new Properties()
propObj.load(new FileInputStream(file(project.property("yourprojectname.properties")))
// now we have 'propObj' object to access keystore.
}
use this propObj to sign app for debug build.
android {
signingConfigs {
release {
//.......
}
debug {
keyAlias 'debug'
keyPassword propObj['keystore.password']
storeFile file(propObj['keystore'])
storePassword propObj['keystore.password']
}
}
I can't find any reason why the store doesn't accept any apks on new apps and others, it every time return please upload another apk
1.0, app code 1 brand new app returns same error with 2 different dev accounts on 4 different vpn(Netherlands/germanmy/singapur..) and 2 different browsers?(opera/safari) also I have deleted cookies etc
my signin in that project is react native
signingConfigs {
release {
storeFile file("key.jks")
storePassword "dosa"
keyAlias "dsa"
keyPassword "dsa"
v2SigningEnabled true
}
}
You will have to set
android:debuggable="false"
in application tag of the manifest file. This is important for uploading your apk.
and if this already set properly and Google Playstore still rejects your APK, then modify your build.gradle
signingConfigs {
debug {
storeFile file("my-keystore-file.jks")
storePassword "my-password"
keyAlias "my-alias"
keyPassword "my-password"
}
}
This will set your own key for debugging.
If your problem still exists then I would suggest reading the documentation, you can read it here it's given properly.
1.0, app code 1 brand new app returns same error with 2 different dev accounts on 4 different vpn(Netherlands/germanmy/singapur..) and 2
different browsers?(opera/safari) also I have deleted cookies etc
I tried with Firefox and it worked thanks...
I am getting this error while i try to run my project from Android Studio to Genemotion. It was working perfectly fine and then I signed the app to test it on other phones and ever since I am unable to run it from android studio. No idea what to do, I tried messing around with Gradle Tasks but they didn't workout.
I have already seen other posts like these Getting error :app-release-unsigned.apk is not signed but they didn't help
I you don't want to add the to your Gradle file the signing information, you can just change to the debug mode for your current build type:
If you want to add the signing information to your build.gradle just do the following:
signingConfigs {
release {
storeFile file("release.keystore")
storePassword "******"
keyAlias "******"
keyPassword "******"
}
}
I'm developing some applications that need system UID. So I made a special keystore file "PFDebug.keystore" made from AOSP's platform.pk8 and platform.x509.pem.
I set it in Eclipse >window >preferences >android >build >cutstom debug keystore. That works fine.
But I am also developing non-privileged applications that use my own debug.keystore file. So I have to change keystore file for each build. I know that default debug.keystore is used when I set blank.
How can I bind debug keystore files for each android project?
It's doable with gradle.
For each project you have a build.gradle in which you can specify a signingConfig. Like that :
signingConfigs {
debug {
storeFile file("../debug.keystore")
}
release {
storeFile file("../prod.keystore")
storePassword 'prod'
keyAlias 'prod'
keyPassword 'prod'
}
}