Rk3568 Android 10.0修改签名文件test-keys为release-keys
前言
在进行Frameworks开发过程中遇到需要适配客户的支付APP,app属于支付型app,估计检测到签名文件为test-keys不能使用,需要使用release-keys,下面将赘述怎么将咱们固件的签名文件从test-keys更换为为release-keys
一、需要参考的文件
修改位置:build/core/Makefile
调用签名文件的位置:/build/make/core/config.mk
二、文件描述
/build/make/core/config.mk
(config.xml中定义系统签名路径):
ifdef PRODUCT_DEFAULT_DEV_CERTIFICATE
DEFAULT_SYSTEM_DEV_CERTIFICATE := $(PRODUCT_DEFAULT_DEV_CERTIFICATE)
else
DEFAULT_SYSTEM_DEV_CERTIFICATE := build/target/product/security/testkey
2.Makefile修改
代码如下(示例):
--- a/android/build/make/core/Makefile
+++ b/android/build/make/core/Makefile
@@ -302,9 +302,9 @@ endif
# Both of these tags will be removed and replaced with "release-keys"
# when the target-files is signed in a post-build step.
ifeq ($(DEFAULT_SYSTEM_DEV_CERTIFICATE),build/target/product/security/testkey)
-BUILD_KEYS := test-keys
+BUILD_KEYS := release-keys
else
-BUILD_KEYS := dev-keys
+BUILD_KEYS := release-keys
endif
BUILD_VERSION_TAGS += $(BUILD_KEYS)
BUILD_VERSION_TAGS := $(subst $(space),$(comma),$(sort $(BUILD_VERSION_TAGS)))
修改BUILD_KEYS的值为release-keys
总结
因为客户的软件是支付软件,为了安全考虑,在test-keys签名的固件上不能使用。
修改完成之后,客户的软件能正常使用了,
每日赠言
当下不杂,未来不迎,过往不念