recently I created a flutter application and tried to publish it, I got 4 files from flutter build apk --split-per-abi and tried all of them, but none of them was installable after downloading from a host, I want to put the apk files on the server to people download and install it, but when I download this with chrome it says:
can't open file
but when I share that downloaded file with telegram and try to install that shared file, there is no problem with it.
what should I do?
notice: while installing I get some security warnings like blocking from play protect
edit: I tried to do that with firefox and that works, it seems the problem is just with chrome
Related
I have followed this tutorial on how to upload an app to Google Play
I have built my app in Android Studio, tested it and it works. I now want to upload the app to Google Play, Amazon App store, Samsung Apps, my own website etc..
After following the instructions down to the bottom on how to sign my app, I click locate file which takes me to 'build\outputs\apk\debug' and the files are app-debug.apk and output.json.
Are these the files for my app and if I want someone to install my app from my website do they download both?
Edit-
After running build again I found another link further down which takes me to app-release.aab, this looks more accurate.
Is this file my app, does it just need to be downloaded on to an android device to run?
.apk file is the file used for the app.
.aab is a bundle file it is used by app stores to distibute diffierent versions of the same app based on device.
I uploaded .apk file to my server. I can then download that file on my android device from my server and it will run the app.
I am trying to build apk for Chinese users. But I found some issue.
When the previous app is built from
Play Store
Android Studio
The apk file doesn't complete installation. And says it's not installed.
However, when I install older one by adb install my_app.apk or download the apk file from the internet and open/install, it installs successfully.
All the apk files has signed key(except for Android Studio build one). And I have no idea what's the problem. Or should it work & Am I wrong? I just tested Play Store one as Internal App Sharing. Since I can't test it out in the real market.
I have an ionic app and built the android release, then did all the key and zip align steps.
Then ran this ~/Library/Android/sdk/platform-tools/adb install (the path on my computer to the apk) (apk name).apk
to test the apk directly on my phone.
I test this on my phone for hours and then go to upload this apk to the google play console and in the android folder the "build" folder that holds my apk completely disappeared. I searched my computer, trash, external hard drive, enabled hidden files, etc. but to no avail.
This build caused me problems building and I don't want to go back and spend many more hours testing so if you have any idea what might have happened or how I can retrieve the build and apk would be much appreciated!
Have you followed the Android Publishing steps here?
When this steps ended, you have example.apk. And you upload this apk with drag drop in google play console version management.
I am using TestFairy for uploading .apk file for testing. Problem is I am unable to download previously uploaded .apk files from older links infact from older links only latest .apk version file is getting downloaded. And version number is showing same for all the .apk file which ever I have uploaded till now. And while uploading .apk file through Testfairy, it says
"TestFairy SDK not integrated in build, no recordings will be performed."
How are you downloading this APK?
If you are using email invites, then the link should work fine with no problems.
If you are using the download page, it might be that you have your download page set to download the auto-update build. Please go to the latest version, and in Build Settings, check the "Upgrade to this build" checkbox.
Webhooks, Testers App for Android and push notifications, you get invited to a specific version, so I don't believe this is the case.
About missing SDK
TestFairy also has an Insights SDK, this SDK will record videos when users are running your app on their devices. It will also handle crashes and it's very recommended you try the SDK to see its benefits. You can install the SDK by simply adding a couple of lines to your Android Gradle and a single line of code. Here is the documentation: https://docs.testfairy.com/Android/Integrating_Android_SDK.html
I have got the solution for the problem from TestFairy team. By changing the versionName every time in 'build.gradle'-->'defaultConfig' solved my problem.
I'm having troubles with APK expansion management in a Phonegap application on Android platform.
I installed the com.flyingsoftgames.xapkreader phonegap plugin and following all the instructions I managed to upload the first APK along with its expansion .obb file.
The first download from the Play Store worked just fine: the app and its extras were successfully downloaded to the device with a single operation.
After publishing an update of the APK and downloading it to the device, the following happened:
I launched the updated application;
The downloader activity of the com.flyingsoftgames.xapkreader started, showing the download dialog;
Since the .obb file didn't change and a copy of it was already present in the local folder, the downloader activity read "Download completed.";
Finally the problem is that the dialog was not dismissed, nor it presents any way to dismiss it manually, so the application doesn't proceed with its launching.
The only way to launch it, is to kill it (in order to stop the "stuck" download activity) and opening it again.
Should I provide a different .obb for each updated version? I don't think so, since this would invalidate the APK+OBB mechanism, conceived to allow for smaller sized updates, as far as I have understood.
Thank you in advance for any advice.
Actually it seemed like a bad installation of the plugin.
I resolved by removing all plugins, rebulding the application for the desired platform from scratch (e.g. phonegap build android) and by re-installing all the plugins.
I noticed something strange though: the installation of the plugin via phonegap plugin installer (with command phonegap plugins add com.flyingsoftgames.xapkreader) installs a different version than the one from the github repository (with the command phonegap plugin add https://github.com/agamemnus/cordova-plugin-xapkreader.git).
So pay attention in case you find different instructions in tutorials and forums.
The version that worked for me was the one from the github repository.