Hello,
I come from expo eject
, before I already uploaded a .aab
file from expo build:android -t app-bundle
when I was still using expo SDK.
I used expo fetch:android:keystore
to get the .jks
file
keytool -list -v -keystore key.jks
gives the same Certificate fingerprints than the Upload certificate on the Play Store Console under Release Management → App signing → Upload certificate
Therefore I guess it’s not a problem with the .jks
file
/android/app/gradle.properties:
android.useAndroidX=true
android.enableJetifier=true
MYAPP_UPLOAD_STORE_FILE=key.jks
MYAPP_UPLOAD_KEY_ALIAS=QGJpZGV0YWdnbGUva2lzc2NoYXQtcHJvdWRjaGF0
MYAPP_UPLOAD_STORE_PASSWORD=*****
MYAPP_UPLOAD_KEY_PASSWORD=*****
org.gradle.daemon=true
org.gradle.parallel=true
org.gradle.jvmargs=-Xmx2560m
/android/app/build.gradle:
signingConfigs {
/*
debug {
storeFile file('debug.keystore')
storePassword 'android'
keyAlias 'androiddebugkey'
keyPassword 'android'
}
*/
release {
if (project.hasProperty('MYAPP_UPLOAD_STORE_FILE')) {
storeFile file(MYAPP_UPLOAD_STORE_FILE)
storePassword MYAPP_UPLOAD_STORE_PASSWORD
keyAlias MYAPP_UPLOAD_KEY_ALIAS
keyPassword MYAPP_UPLOAD_KEY_PASSWORD
}
}
}
I didn’t notice any change during ./gradlew bundleRelease
when I purposely put wrong passwords in gradle.properties, does it really sign something?
Is there a way to see the signature on the .aab file with linux?