google-play

问题 As far as I remember, 10 years was the default setting when creating a keystore in Eclipse. I think, about 5 years ago, Android development got kind of mainstream so I expect a lot of apps to be un-updatable in the Play Store in 5 years. So far, I haven't found a solution on how to "prolong" a certificate's lifetime. Is there one? Will Google implement a way to set up your app with a new certificate? Of course, my scenario doesn't affect TOO many apps but I think there will be a considerable

问题 As far as I remember, 10 years was the default setting when creating a keystore in Eclipse. I think, about 5 years ago, Android development got kind of mainstream so I expect a lot of apps to be un-updatable in the Play Store in 5 years. So far, I haven't found a solution on how to "prolong" a certificate's lifetime. Is there one? Will Google implement a way to set up your app with a new certificate? Of course, my scenario doesn't affect TOO many apps but I think there will be a considerable

问题 As far as I remember, 10 years was the default setting when creating a keystore in Eclipse. I think, about 5 years ago, Android development got kind of mainstream so I expect a lot of apps to be un-updatable in the Play Store in 5 years. So far, I haven't found a solution on how to "prolong" a certificate's lifetime. Is there one? Will Google implement a way to set up your app with a new certificate? Of course, my scenario doesn't affect TOO many apps but I think there will be a considerable

问题 As far as I remember, 10 years was the default setting when creating a keystore in Eclipse. I think, about 5 years ago, Android development got kind of mainstream so I expect a lot of apps to be un-updatable in the Play Store in 5 years. So far, I haven't found a solution on how to "prolong" a certificate's lifetime. Is there one? Will Google implement a way to set up your app with a new certificate? Of course, my scenario doesn't affect TOO many apps but I think there will be a considerable

问题 While updating an app with "Timed Publishing" on Google Play, after I upload the APK, should I select the "publish now to production" option? Will this submit the new APK to production or will Google play just process it and wait for me to click "Go Live". There is no clear step by step instructions on Google or anywhere else. It is critical that the app does not go live for my company so I am not ready to take chances by clicking that button. 回答1: When uploading a new APK and pressing "Start

问题 Is there any way to know if an application has been downloaded from Amazon App Store or Google Play Store? I meant within the app itself, of course. I have deployed an app to both sites and I rather like to know from where the customer has downloaded it within the application. I know, I can deploy different applications to each service, but this adds some maintenance work that could be avoided if there were some manner to solve it just with a conditional within the app using the same package.

问题 Is there any way to know if an application has been downloaded from Amazon App Store or Google Play Store? I meant within the app itself, of course. I have deployed an app to both sites and I rather like to know from where the customer has downloaded it within the application. I know, I can deploy different applications to each service, but this adds some maintenance work that could be avoided if there were some manner to solve it just with a conditional within the app using the same package.

问题 I have used PWA2APK to upload the first version of my React app to Google Play. It worked great. But every time I try to update the app by uploading a new version, I get the following: You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint: SHA1: ******************* and the certificate used to sign the APK you uploaded has fingerprint: SHA1: ********************** Your APK or Android App Bundle needs to

问题 I have used PWA2APK to upload the first version of my React app to Google Play. It worked great. But every time I try to update the app by uploading a new version, I get the following: You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint: SHA1: ******************* and the certificate used to sign the APK you uploaded has fingerprint: SHA1: ********************** Your APK or Android App Bundle needs to

问题 I have created an internal release of an Android app on the Google Play console. When I copy the opt-in link and paste it into the browser, and then click the link to install the app, I get this Not Found page. According to the Play Console, the Internal Testing Track is not active, but it's been 5+ days. Here's what's not the problem: All the app details are filled in, and the Play Console says the app is available to internal testers I am logged into a Google account that is on the internal