Android: republishing a .apk file to the store - android

I submited an .apk file to the Android app store yesterday, and now submitted another one.
It created a second apk file which I activated and then I de-activated the previous one.
Is that the right procedure? Now I have 2 apk files showing up. Is that what is supposed to happen? Or is one supposed to delete the previous file?
Thanks!

Well it seems to be the right and only way to do it, because google dont seem to allow deleting files only to unpublish them. Perhaps to guarantee that free apps can not be sold..
See this from 2010, probably stil valid because I can't find any delete button either.
how to Delete published application from my android market account?

Related

Sketchware - Issues Publishing to Play Store

Using the Sketchware app and Android, I am trying to export to the Google Play store, I have to select the .json for the service account to allow it to publish the app.
However, when I try to select the .json file I have downloaded to my phone, I navigate to the directory the .json file is stored in then when I try to click on it, it is greyed out and I cannot click on it.
(P.S.: I have tried contacting Sketchware support. However, it has been over three days now and I understand due to coronavirus the response may be delayed, but I thought I would ask here if anyone has a solution.)
Why are you publishing the app directly from Sketchware to PlayStore?
You better sign the apk usin APK SIGNER app and manually upload the APK to the Play Console.
I have never used Google Play Console before, but I think this could help you:
Download your app
Using Apk Extractor (play.google.com/store/apps/details?id=com.ext.ui) is a software that will help you to get APK file from an pre installed app from Android ONLY. Using this software you can actually get an APK or Android Package that you can use while publishing app
There are many application available on Google Play that can convert your app file to AAB format.
Yes, download Apk editor and select generic key or test key (try them out, there's a few) in settings in the app, and edit the API version to the correct number. And set up a Google Play console account.
Yes, we do have a solution. Send the file to WhatsApp. Then share it from WhatsApp, choose file manager, copy the file to the place that you want, open sketchware, choose the file that you added in the JSON file, and enjoy.

Create a patch APK file

Assume that "app-v1.apk" has assets/a.png. user install this app.
then we delete "a.png" file from assets and generate "app-v2.apk" file.
Is there any way to access the "assets/a.png" file when the user updates the app?
As far as I understand your question, what you are trying to say is
can we access assets of previous build that are not present in current build?
As far as my knowledge goes, The answer is NO. Play store manages updates so when you upload the new apk playstore updates app with current build, so the assets or changes in the old build are not accessible anymore.
Hope this answers your query.
I think it's not a good idea. You have to provide a complete app to take into account new users. Moreover, Play Store is able to update an app incrementally so you don't have to care about duplication for your users

Android update on Google Play - want to delete old data

I'm going to release new update of my app on Google play store. I use some resources stored on user's SD card (\sdcard\Android\package\data...). I make some important updates and want to replace these old files. Is there any way to delete all these files before updating? (Some flag "delete old version's files" on GPlay) Like uninstall and reinstall of the app. I can do it my way in app (try to delete old files if present). But this approach (via some installation routine) is smart, I think.
You should do it by yourself, because Google Play Store wouldn't do it for you.

Attached apk file remains non updated

I am facing this problem so many times,
I used to send the apk files through mail to my clients for reviewing.
Sometimes , they are telling that the new attached one has not get any updates , it remains same.
Even i did updates in that and, i have chacked it by uninstalling the older application and downloaded the attachment , So it was working fine with updates in myside.
I asked them to do same. But for them it wasn't.
So please give some idea,
Is there any better way to share the apk files?
Are they need to clean some other folders in their mobile, like "temp and cache" in PC?.
Or I missed somewhere in the Updated builds?
Please it is very difficult one for me to face always.
Thanks in advance.
hmm.. instead of sending the .apk file to them through email, why not upload your .apk file to a server or website folder and let them install from there using their phone / device.
in android, you can install apk files from the internet right :)
that way, you can just send them the link of the updated version of your app.
Maybe the problem there is your apk sent to their computers, is either not really saved / not overwritten. in case the .apk file has same filename.
you can try to change file name also
:)

How do I save the screenshots and meta data before submitting ANDROID?

I do not have the final APK file yet but I want to start adding the screenshots and other information ahead of time. There is a "SAVE" button and I am assuming this should be possible but it's not allowing me to save without the APK AFAIK...
You will need to upload a draft APK (never has to see the actual market) in order to get started. The only thing that MUST be correct here is the package name your app will use, as this is needed to create the new record, and is read out of the APK file rather than allowing users to enter it manually. Nothing else about the application has to even resemble what your final will be.
With the draft in place you can start updating all the other meta data and using the Save button to save your work. When you upload the final APK file, you may then click Publish.
Unfortunately, you have to upload all the information at the same time. This makes sense though, if you put an app on the market that people could search, but didn't actually include the apk...well that would just be super confusing to anyone on the market.
You could save your draft with a draft APK and then make sure to update the APK with your final one before you publish.

Categories

Resources