更新时间:2023-12-03 09:19:52
既然你只与签订APK有这个问题,看来你已经配置了不正确的释放键的哈希值。
尝试检查密钥库的版本密钥散列值用于注册的APK在您的 LinkedIn应用的配置作为的文档:
生成释放键散列值
要生成释放键的哈希值,请使用以下命令:
密钥工具-exportcert -keystore YOUR_RELEASE_KEY_PATH -alias YOUR_RELEASE_KEY_ALIAS | OpenSSL的SHA1 -binary | OpenSSL的BASE64
配置值在您 LinkedIn 应用的的结构中,提供一种在一个或多个值 以下逗号分隔的格式:
Android.Package.Name,键哈希值
I am integrated LinkedIn
successfully using newly released Android Mobile SDK
and all done well using Android Studio
, but when I generating signed apk
is showing the below mentioned error. I heard that we have to use debug.keystore
file otherwise this error LinkedIn sdk will return same error.
I have done that too, but the scenario was while we are generating signed apk in Android Studio it's giving .jks file
not .keystore file
. Please tell me the step how to generate .keystore
file and how to configure this in build.gradle
.
Error:
Error={
"errorMessage": "either bundle id or package name \/ hash are invalid, unknown, malformed",
"errorCode": "UNKNOWN_ERROR"
}
My gradle file look like below, and I pasted the .jks
file inside app direction, but still while installing signed apk
its not running giving the error as I mentioned, but it working fine when installing the app in debugging mode.
build.gradle:
allprojects {
repositories {
mavenCentral()
}
}
apply plugin: 'com.android.application'
android {
compileSdkVersion 22
buildToolsVersion "21.1.2"
defaultConfig {
applicationId "com.myapp.hello"
minSdkVersion 14
targetSdkVersion 22
versionCode 1
versionName "1.0"
}
signingConfigs {
sdkTest {
storeFile file("secureln.jks")
storePassword "password"
keyAlias "secureln"
keyPassword "password"
}
release {
storeFile file("secureln.jks")
storePassword "password"
keyAlias "secureln"
keyPassword "password"
}
}
buildTypes {
sdkTest {
debuggable false
signingConfig signingConfigs.sdkTest
}
release {
debuggable false
signingConfig signingConfigs.release
}
}
}
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar', '*.aar'])
compile project(':linkedin-sdk')
}
configurations {
}
dependencies {
compile 'com.android.support:appcompat-v7:22.0.0'
compile 'com.google.code.gson:gson:2.3.1'
}
I need to any one help me please.
Since you have this issue only with signed APK, seems you have configured an incorrect release key hash value.
Try to check that the release key hash value of the keystore you used to sign the APK is correctly listed in the "Android Package Names and Hashes" field of your LinkedIn application's configuration as described in the documentation:
Generating a release key hash value
To generate a release key hash value, use the following command:
keytool -exportcert -keystore YOUR_RELEASE_KEY_PATH -alias YOUR_RELEASE_KEY_ALIAS | openssl sha1 -binary | openssl base64
Configure the valuesIn the "Android Package Names and Hashes" field of your LinkedIn application's configuration, provide one or more values in the following comma-separated format:
Android.Package.Name,Key-Hash-Value