I am developing an Android application and in this application, I am using "In app billing" features.
I uploaded apk on the google console account and set the product id, price and other required things and saved all the data in the draft.(Application is still in draft mode).
I did not publish my app yet.
After a few minutes, I realized that I uploaded old signed apk file and keystore of this apk has already lost.
Now I want to remove this old apk file and want to upload a new one in draft mode.
My problems are :
How to remove the old apk file from the google console account.(In Draft Mode)
How to upload the new signed apk file with new key store (As I have
lost my old key store)
EDIT:
I want to publish the app with the same name and with same package name. I do not want to change my app name atleast.
This can now be done by going to Release management > Artifact library and deleting the APK.
You cannot delete the artifacts anymore.
Here's a part of my chat with Pete through the built-in help & support.
Pete:
Thanks for waiting. You can't remove an apk that you've already
served. Your next Production apk has to be version code 3 or higher.
Me:
So I can't just delete the artifact of that build?
Pete:
That's correct.
(P.S. He mentioned version code 3 because of my specific issue)
You can try KOTIOS's answer.
Delete the aab / apk file from the Google Play Console on the App Bundle Explorer under Release Tab
Then select the apk/aab file you want to delete from the List
Quoting Can we still remove never-published apps from Google Play?:
Well, the answer is that the strategy still works. If you've never
published the app, you can remove all traces of it from Google Play
and another publisher account can then upload an app with the same
package name. All you need to do is deactivate (if necessary) and then
delete all .apk files and the app will disappear from your developer
console.
If the app was ever published, this will not work. You can unpublish
an app, but you cannot delete any .apk files that were ever active
while the app was published. (This behavior is undocumented as far as
I can find.) This is unfortunate; it would be nice to be able to
completely remove all traces of an app that was never downloaded by
anyone. Even better would be a sandbox area that emulated all aspects
of Google Play, including buying your own app (and would support doing
it through the emulator).
I also discovered that the delays involved in propagating changes to
all Google Play servers seems worse than it did a year ago with
Android Market. In one case, when testing license responses I had to
wait two hours after uploading (but not publishing) an app before the
response came back as anything from "NOT_MARKET_MANAGED".
You can do this by upload new apk with upper version
and the old Apk will deactivated automaticly
Related
Here I am developing Android app with android studio. I turned my google account into a google developer account and then published my app in the play store after signing that app within my computer. After a month I published an update for that app with the same package name. I also upgraded the "Version Name" & "Version Code". I checked the the situation by using a phone which has the initial release of the app, but after I released the update the specific page of that app in play store doesn't show an update button ("open"button is there).
How can I correct this?
Thanks.
If your phone with the "initial release" of the app didn't install it from the Play store, then the Play store won't update it. I suspect this will be your problem.
The Play store will only update apps for which it did the initial install (to avoid treading on the toes of app developers during development or other app stores).
The way it checks for "Did the Play store install this" is "Does the signature of the app match the signature in the Play store" and "does the user on the phone have a record of install from the Play store on their account on any device".
After updating an app on play store it can take several hours to be available on play store. Just wait for couple of hours.
So first of all you have to make sure the following three points are in place:
You are installing exactly the same variant from android studio compared to the one you published on google play store.
The app you installed from android studio has a lower "version code"
You are using exactly the same signing key.
Most likely the third point is what is stopping this from working. The problem is that if you are using app bundle as publishing format, that apk is not created yet when you upload the bundle and it will only be create and SIGNED at a later the stage, when the app is about to be distributed on a specific device.
Unfortunately, there is a chance, like in my case, that the signature still will not match perfectly even if you used exactly the same key to sign the app, reason being that if you have singed up for Google Play Store signing, google will add some metadata: "It does however insert a minuscule amount of metadata that helps with verifying the source and integrity of the distribution. This metadata comes in two flavors: For all apps uploaded to Google Play, Play has been adding security metadata after the signing block to enable features such as authorized P2P app sharing. We announced this originally in a blog post in 2017. For apps uploaded as app bundles, we will improve this security by introducing what is called a source stamp. This source metadata is inserted into the app’s manifest by bundletool. When the APK is generated on Play’s server, it’s also signed with a Google key in addition to your app signing key."
I yet have to solve this issue unfortunately
A teammate put the APK in the wrong account in Google Play, now, I need to fix without the original binary. So, I want to know if I can download the APK out of the wrong account, then signon with the correct account and upload?
FWIW - the APK is not yet published, it is still a draft as we need to put the remaining required collateral from Marketing team.
remove APK from wrong account draft.
create APK with correct account signature and upload there.
No, you cannot download the API from the dashboard. Probably would be some sort of a security violation if it were allowed.
This sounds like a re-marketing ploy (app rustling). It takes an app from one account and replaces the branding (names, images, etc) with that of another account.
If your devs do not archive their published works, then they are silly persons. What do they use for a code repository? A sock?
Google only stores the latest version of an app apk. Previous app versions are tracked, but the previous apks are not archived (as far as puny humans are concerned).
Only the latest published apk can be downloaded, and only as a customer.
There is no Wayback Machine for android apps, afaik.
I have already published an app to version 2, and have uploaded an app with version 3 to to Google Play as a beta testing version, and then discovered with errors, so I have modified the codes is now ready for publish.
I tried to upload the correct apk with version 3 to Google Play, but it says I have already uploaded a version 3 apk already.
Question:
How to remove the wrong apk from the Google Play? Or what should I do? Or I can only modify and upload the app as version 4?
Thanks!!
You can not remove the apk from google play. You just have now update your application version and upload the new apk on google play that is the only way.
Please note that package names for app files are unique and permanent, so please choose wisely. Package names cannot be deleted or re-used in the future. Keep in mind that if you've lost your keystore, you'll have to publish the app with a new package name and a new key. You should also update the description of the original app and unpublish it.
If the app was ever published, this will not work. You can unpublish an app, but you cannot delete any .apk files that were ever active while the app was published. (This behavior is undocumented as far as I can find.) This is unfortunate; it would be nice to be able to completely remove all traces of an app that was never downloaded by anyone. Even better would be a sandbox area that emulated all aspects of Google Play, including buying your own app (and would support doing it through the emulator).
Check out HERE
My application is currently in alpha. On the google play developer console, I accidentally uploaded a new APK as production rather than alpha.
In advanced mode, there is a deactivate button. But if I deactivate and try to save I get the generic message "The application could not be saved. Please check the form for errors." I don't see any errors on the form. How do I deactivate?
I tried uploading a later version to alpha - that seems to work - but I don't want ANY version in Prod, as my app is not yet ready for prime time.
According to a Google customer service rep I contacted:
The Deactivate button is provided in your advanced mode when you want to support multiple APKs but when your new update supports the same number of devices as your previous APKs, the system won't allow such update. So it is required for you to deactivate the older version in order to upload your new APK.
The Deactivate button is only useful for situations where you have multiple active APKs.
Furthermore, discussing with them, there is apparently no functionality at this time that allows for you to remove APKs from the Production tab once they've been uploaded to that tab, AND there's apparently no way to enable Beta testing if your app is unpublished, so at this point it seems there's no way to undo what you've done if you accidentally upload an APK to the Production tab by mistake. The workaround proposed by the representative was to change the package name of the app, change the keystore used to sign, and create an entirely new application.
Further discussion with the representative indicated that the "error" is that you can't have a Production tab without an APK if there was one there already, but it sounds like there's a bug in that it doesn't actually report that that's the cause.
In latest play console you can goto Publishing Overview->managed publishing status-> press manage button on right then turn on managed publishing
So I'm having trouble uploading a new APK to the play store with billing enabled.
Currently I have a published app that is paid and I want to change it to a subscription app such that the users get a yearly subscription and hence latest data to the app.
Now my issue is that the developer console will not let me upload a draft APK with the permissions for billing enabled. I log into the dev console, go to APK, change from simple to advanced mode, save my new APK as a draft and once uploaded I get the following error:
This configuration cannot be published for the following reason(s):
All devices that might receive version 1 would receive version 2.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code.
I updated the Version code and the version number to be one higher than the current as well as different combinations of upping only one of the two values with still no success.
The app is being signed with the same keystore.
Thanks,
DMan
Figured out what this actually means now. Basically it was just telling me that I need to archive the current apk in order to actually publish the new apk. The new apk was successfully added as a draft. This message was just worded a little awkwardly and actually means that in order to publish version 2 version 1 must be archived NOT that there was anything wrong with the saved draft I performed.
Thanks,
Dman
Yes, all you have to do is to disable the old aplication, after that a the Publish botton will be available to push on the top left area so your new APK will be published
Did you disable your first version? By default, after uploading in advanced mode, both your first and 2nd version are activated. Looks to me like it's just saying that you've got 2 APKs active, that will reach the same devices thus one of the 2 is useless.