android-app-signing

When I upload the output of PEPK tools, Google Play Console says “The certificate provided is invalid. Please submit a different certificate.”

血红的双手。 提交于 2021-01-28 11:51:09
问题 This is the command I executed in my computer according to Google Play: java -jar pepk.jar --keystore=foo.keystore --alias=foo --output=output.zip --encryptionkey=blabla --include-cert and I uploaded the output.zip . Google Play Console told me that: The certificate provided is invalid. Please submit a different certificate. Besides, there are two files in the output.zip : certificate.pem and encryptedPrivateKey . 回答1: I think this happens when your key expires too soon. Did you create your

How to add multiple SHA1 fingerprints to my Android App for testing?

耗尽温柔 提交于 2020-07-08 09:33:24
问题 My Android App already has a SHA1 fingerprint on Google developers console generated by another developer some time back. Now, I am debugging Google Sign-in bug in the App and it turns out that Google Sign in uses the default SHA-1 found in .android/debug.keystore to make a request in the OAuth authentication process. And I had generated a new debug key yesterday because after all it is debug. How do I add or incorporate this new debug key to Google's developer console to make a successful

Use provided upload_cert.der to sign a release Android APK file

邮差的信 提交于 2020-01-02 03:33:47
问题 I've just enrolled in the Google Play App Signing program, which required uploading an encrypted version of the release keystore and had an "optional" step for creating an upload keystore - optional is in quotes, because I think it should be a required step, but anyway, after a successful enrollment, I'm now left with an Upload certificate , which I should somehow use to sign my future app releases. What I've done so far: I created a new keystore from Android Studio, set the store and alias

Getting “The AndroidManifest.xml of the uploaded APK could not be parsed. Was it compiled properly?” error after enabling Google App Signing

梦想与她 提交于 2020-01-01 08:59:50
问题 After enabling Google App Signing, everytime I try to upload a signed release APK to Play Store I get an error saying The AndroidManifest.xml of the uploaded APK could not be parsed. Was it compiled properly? . Here is the Android Manifest file got from the signed APK with the APK Analyzer tool <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" android:versionCode="227" android:versionName="4.9" package="com.myproject"> <uses-sdk

Google Play App Signing and Instant Apps

北慕城南 提交于 2019-12-31 03:05:10
问题 Fairly straight forward question. Does anyone happen to know if Google Play App Signing supports Instant Apps? The reason I ask: Enter your app’s signing config, or select a keystore file. While it’s possible to use a debug config or keystore during testing, the generated Digital Asset Links file won’t be compatible with the release version of your app. If you do upload a Digital Asset Links file that uses a debug config or keystore, then before publishing your app you’ll need to generate and

Google Play App Signing - Can't upload update

Deadly 提交于 2019-12-24 18:23:29
问题 Alright so this is the error I get when uploading the APK to Google Developer Console; Upload failed You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s): [ SHA1: Numbers go here ] and the certificate(s) used to sign the APK you uploaded have fingerprint(s): [ SHA1: different numbers go here ] However, I know for a fact I'm using the same .keystore I

Test Google Play Games on app signed with upload key

笑着哭i 提交于 2019-12-22 09:48:08
问题 I am trying to test the functionality of google play games on the app I am currently building with Unity. I have opted for the Google's app signing and have access to only the upload Keystore. Is there a way to connect to google play games with a version of the app signed by the upload key so that I don't have to deploy my app everytime I want to test it? 回答1: Though it's not the ideal workflow, you can upload an APK (signed with your upload key) to an internal or closed test track, and then

Sharing android debug certificate across different developer machines in Android Studio

余生颓废 提交于 2019-12-22 06:59:28
问题 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. 回答1: 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