I have the application that has '16' mini sdk and '27' targeted sdk versions. When I install the application with USB cable from android studio, it works fine. But when I send the application to other phones b/n 16-27 sdk versions, It appear
App not installed
error on the phone. I had used xender to send the application.
My sdk versions are here :
Sometimes App not installed occurs when a same version of the app already exists.
Either increment the versionCode of the app or uninstall the
previous app.
After that, create a signed apk using
Build->
Clean Project followed by Build->
Generate Signed APK
After looking at the screenshot (build.gradle) you shared here, I might advice to put versionCode after versionName. That way, you don't have to bother about what versionCode is written in AndroidManifest.xml.
Based on your comment the problem is that you are using a build built by Android Studio.
Android Studio will add a testOnly attribute so that's why you can't install it on other devices by default.
You need to send a build built by Build -> Build APK(s) or Build -> Generate Signed APK to be able to install it on devices.
Related
We use Firebase App Distribution to deliver staging builds. Android devices below Android 12 can install it successfully, but on Android 12 it says "Installation failed".
Important notes:
No other versions of this app installed on this device
If we manually download debug or release APKs for this app they also install
We upload APKs to Firebase
Is there any Android 12 limitation I miss? Is there something new in Firebase what prevents us from installing APKs from it on Android 12?
I found the problem, if you target Android 11+ and distribute you have to use app signer to sign your APKs. In Bitrise CI you need to add use_apk_signer: true field to sign_apk step.
When trying to manually install an apk (v2.0) over an .apk (v1.0), I get the error "APP not installed" error on my device.
I should note that both of the .apk are the same app, only the version is upgraded.
I am also using release version of the apk and I don't want to uninstall the existing app (just upgrade).
Can anyone help me identify what might be the cause of this problem?
Thank you.
upgrade app scenario works when the version code of both the apks should be different. The incoming version should have a higher VersionCode (not VersionName) than that of the existing app. Just Verify that versionCode of both the apps are different. This can be verified by play store console (for the existing build from play store) and app > build.gradle
I launched and debugging my application successfully by Android Studio via USB.
But if I copied APK from \app\build\outputs\apk the application crashed after installation.
What's difference between installed APK and launched via Android Studio?
How to fix trouble?
try enable multidex
defaultConfig {
...
// Enabling multidex support.
multiDexEnabled true
}
try also Disable InstaRun
Go to Preferences and find the Instant Run option under Build, Execution, Deployment. Uncheck the check boxes to disable instant run
clean and delete debug.apk.
and try Build>BuildAPK again
Hope it works. . if stills fail then you should make release apk instead.
Not sure if this is what is causing your trouble but when I had my app installed on the system and didn't change the app for a signed one it'd crash.
So what I'd do is to make sure that the app is uninstalled from your phone and then build a signed APK to use.
Delete debug.apk from output folder under build in app. Generate again using Build->Build APK option and install again.
Have these erro when i'm trying to build the apk to some devices. Have no idea whats going on.
I get that when i build and install apk on device at the first time.
Someone have some tips for that?
[[EDIT]]
Well, after creating a debug key on keystore, i can build and deploy the apk via ADP to the device. But, dont know why, the error just return...
And now, we have other error:
UPDATE:
I Fix that issue removing all Android SDK and Android Studio and ReInstall it.
The problem can be solved by addding the install flags -r -t in the Run/Debug Configuration Dialog like it's showed in the given image
You can find Run/Debug Configuration Dialog location here according to Jetbrains.
UPDATE: Depending on the Android Studio version the Run/Debug Configuration position in the IDE can be slightly different, but always refer Jetbrains to find whatever you are looking for
When you've installed an APK from another source, Android Studio warns you before overwriting.
For example, if I've developed an application, uploaded it onto the Google Play Store, downloaded it, then try to re-deploy that same application from Android Studio, I'll get this warning.
It's trying to tell you that the way the package is signed is different; it's warning you that another app might be masquerading as the original.
The reason is you are trying to install the application with the same package name.
If you have already downloaded the same application from the play store /app market, then simply uninstall that application and RE-RUN.
This error can also occur if you recently switched branch which had different build variants declared in build.gradle file and you didn't perform gradle sync.
For example you had release and debug and then you switched to branch which has releas, deubg and staging variants; your project will still build but while installing apk this error can pop up.
I installed the app through android studio and its working fine, but when I create the apk and then I installed the apk, on some devices my app is crashing.
Can someone know how we can see the logs or errors in case when we installed through apk, in can't debug the app bcos its working that time.
here are few details,
build variant: debug,
my apk name: app-debug.apk,
and I am using 2 3rd party libs as an .aar files
If you have installed the apk also you can able to get the logs if you have connected your device with studio. For that you have set the No Filter in Android Monitor.
In the phones, your app is crashing, don't just install the app by apk there. May be some of your 3rd party dependency is not compatible with those versions or phones.
Debug your app in those phone with cable and check error logs. You will get to know the problem