After switching from Eclipse Classic to the Eclipse ADT Bundle I made a few minor changes to an existing app today. I tested it on my physical device, everything worked as it should, so I exported it as a signed APK to upload to Google Play. When uploading, I noticed that the APK was only about 300kB, compared to the 700kB of the previous version. I had a look inside the APK-file and noticed that in the old version I have libGoogleAnalyticsV2.jar and a folder called javadocs (which seems to come from the Google Analytics install). These are not present in the new build, hence the smaller file size.
Don't I need the .jar file to be in the APK for things to work? Or was it just added to my old APK by mistake, taking up 400kB for no reason at all?
The new build appears to be working fine, but I feel a bit hesitant to upload it to Google Play until I know what's going on...
Related
I tried to upload an Android App Bundle (for an existing app) on the Google Play. I have done the google signing part, And it says Releases signed by Google Play. Buy after i upload my aab file to the release, it said that "you uploaded a file that is not a well-formed zip archive". Anyone knows why this problem occur, and how i can fix it?
Thanks for your help!
My problem with this one was very peculiar.
Scenario was next: I needed to upload aab file, which needed to be downloaded from our Jenkins server. What was happening is that for some reason it wasn't downloading the full aab file, but a reduced amount of data. In the download folder I had some previous versions of those files, so I assume some sort of optimization took place in the background due to the nature of those archive files. For example Jenkins showed 30MB, and my downloads were 15MB, or even less if I had more aab files in that folder. Even deletion of them didn't work.
What worked eventually was deleting those files from Trash (I'm using Mac), and attempting download after that.
I'm using the Firebase App distribution to send out updates to a few testers and the most recent APK I uploaded will not install on Android devices (actually it is several new versions that all have issues installing). I had previously uploaded a version that worked, but all subsequent updates fail with an 'App not installed' error message. I'm confused by the APK files that are generated from Android Studio and I don't recall which version I previously uploaded that worked. In the apk folder there is a debug folder that contains an apk file named app-debug.apk. I'm pretty sure this is the one I used with the successful version of the distribution. There is also a flutter-apk folder with an identically named file app-debug.apk. Does anyone know the difference between these files and which one I should use? That question is a side note as neither of those files work.
I have tried telling my testers to uninstall the previous (working) version and then try to update their Android with the latest version, but the error still occurs. I do not have any issues with my iOS version and that test group.
Do I need to update the debug.keystore file? I have searched many different threads for a solution and nothing seems to work. Any suggestions to debug the issue would be appreciated.
On Android, if the package exported by debug cannot be installed on some devices, such as "parsing failure", you can add a signature file to the debug version. It is better to generate it yourself, and do not use the tool's own. In addition, you can add a signature file to the debug version androidmanifast.xml Statement under application android:testOnly= "False", which may help you
This may seem like a duplicate question, as there are 4 or 5 other exact questions. But I have tried the solutions to every other question like this with no luck.
Basically, I've been successfully generating signed APKs for weeks now, but out of the blue 3 days ago the signed APK is not being generated. Simply nothing gets generated, even though Android Studio says that it has successfully generated it.
I am using Android Studio 3.0.
I have tried totally uninstalling/reinstalling AS, I've made sure that both APK option checkboxes are checked during the signed APK generation dialog window.
I have many times restarted Android Studio and my computer, as well as cleaning/rebuilding many times. I do not know what to do from here.
I really need to get an update of my app out to Google Play but I cannot generate the new APK.
The apk is probably being generated but not on the path you expect. Look around the project subdirectories or search for apk using your operating system search tools.
I too faced the same issue, what you need to do is after migrating a project to Android studio 3.0, delete the already generated signed apk in path /project/app and generate the signed apk again, you will see a release folder in the same directory.
I have a "draft" APK in my Google Play console, and it's connected to an APK expansion file.
The version code is 9, and the expansion file is "main.9.com.something.something.obb".
Now, I'm trying to update the APK before I release. I increased the version code, along with some code changes.
When I upload the APK, I choose to use "main.9.com.something.something.obb" as my expansion.
Now, Google Play tells me this:
This configuration cannot be published for the following reason(s):
Version 9 is not served to any device configuration: all devices that
might receive version 9 would receive version 10.
But if I try to delete version 9, it won't let me, because it says that there are other versions depending on its expansion file!
So it's an infinite loop and I can't update my APK. The only solution I found is to re-upload the APK expansion (400MB), which is unacceptable. I don't want to do this every time I update the app, because users will need to re-download the expansion.
Also, I'm almost sure that this was never like that, and it's a bug that got introduced in the last period. I remember APK options like "deactivate" and so on, and now I can't find them.
Any help?
I actually solved this a few months ago but forgot to post the answer here.
I contacted Google Play support, and they clarified to me that this behavior happens only in "draft" mode.
Once your app is published, you can update your APK without touching the expansion file, and reference the previously stored file.
My app is now published and there were no problems after moving from "draft".
I upgraded my Eclipse ADT tools to r20 (from r17 or so) and now the applications installed on the devices use twice the size of the apk. The app itself is running fine.
This happens for both the release and the debug versions, and whether I generate the apk with ant (and install thru usb) or launch the app from eclipse.
I tried with various target versions but it's always the same thing.
For info
- I do not use "copy protection" nor licensing, this is direct install, not thru the play store.
- I use proguard to optimize/obfuscate my code. I uncompresed/analyzed my apk and everything seems normal (compared to previous apk that do not exhibit this issue).
Thanks in advance for any info on that.
Installed app's size is always larger than apk. becoz apk is just a zipped file(copressed file) and installed app is unzipped(uncompressed).
Found out the issue.
At the same time as the sdk update, the manifest had been updated, and the preferred storage option (external) had been deleted, So it was installed entirely on the phone memory. and the memory reported in the app manager was double the apk size.
Now it is installed on the SD card, and it uses almost the apk size in system memory as before.