英文:
What is defines the User aspect for the generation of Settings.Secure.Android_ID
问题
我刚刚完成了对一个新版本的安卓应用进行的测试，并生成了一个已签名的apk文件用于发布。我注意到，与当前在应用商店上发布的版本相比，Settings.Secure.Android_ID生成的值是不同的，尽管它们都是由相同的密钥签名的。
我想知道这是否是因为我通过侧载apk而不是从应用商店安装，我的想法是ANDROID_ID生成的"用户"方面受到应用商店用户登录状态的影响，而通过侧载apk，用户是不同的。
我在同一部手机上安装了已签名的APK和当前的应用商店版本，它们都生成了相同的ANDROID_ID，但它们彼此不匹配。
英文:
I am just finishing up testing on a new version of an android app and have generated a signed apk for release, I noticed that the value generated for Settings.Secure.Android_ID is different to the version that is currently live on the play store despite being signed by the same key.
I am wondering if this is because I have side loaded the apk rather than installing from the play store, my thinking is that the "user" aspect of the ANDROID_ID generation is influenced by the play store user signed into the play store and by side loading the apk the user is different.
I have installed the signed APK and the current play store version of the app on the same phone and both always generate the same ANDROID_ID but they don't match each other.
答案1
得分: 1
所以正如@ShlomiKatriel提到的，当Google批准并发布您的apk时，他们会对其进行签名，因此Play商店版本将生成一个与侧加载的已签名APK不同的ANDROID_ID，但密钥始终相同，因此ANDROID_ID也相同。
英文:
So as mentioned by @ShlomiKatriel Google signs your apk when they approve it and put it live so the playstore version will generate a different ANDROID_ID than the signed APK that is side loaded but the key is always the same and as such so is the ANDROID_ID.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论