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.
Related
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 want to run my application in phone but I get following message:
Installation failed with message:
INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package signatures do not match
the previously installed version; ignoring!.
It is possible that this issue is resolved by uninstalling an existing version of the apk if it is present, and then re-installing.
WARNING: Uninstalling will remove the application data!
Do you want to uninstall the existing application?
In my phone I have installed previous version of app from google play. I know that uninstalling old version of app from my phone can fix the problem but I don't want to do this because then I might lose all app specific data.
What I tried:
generating signed version of app using the same keystore.jks like previously
changing versionCode and versionName in build.grandle file and then generating new version of app
And still I have the same problem. What should I do to update my app without losing data?
There are two possibilities I can think of
You use Google Play App Signing. If you use Google Play App Signing then the signature in apps coming from Google Play will always be different to the app coming from your IDE. The only way you can get the update to work is to update the app from Google Play. The best way to do this during development is to use an "Internal test track". Google launched these at Google I/O this year and they let you update your app in seconds from Google Play. So when you have an update, don't install from your IDE, upload to Google Play internal test track, republish, and then update from Google Play. It is really quick.
You don't use Google Play App Signing, but you are trying to install your debug build instead of your release/production build. Make sure you are building the production release APK, so it is signed with the same key as the one uploaded to Google Play.
If I'm understanding correctly you want to re install the "same" apk in your phone but with some changes in the code (updates) but Android Studio can't install the new apk.
I can only think in one thing, this is the explanation:
Please remember that android has different "Build Variants" there could be many but you will always have "debug" and "production" build variants, as I can read, you have installed the one in Play Store this means that you have a "production" build variant already installed in your phone, so you need a new "production" variant version of your app with the same build data (code and name version) and the updates in the code.
Build a signed apk with the same data as the previous version (code and name version) (Just like the one you used to upload to Play Store).
Find the signed apk.
Use adb to check your connected devices, expect a list
adb devices
Use adb to install this new apk.
adb -s <device_identifier> install <apk_name_include_apk>
Following those steps should let you install what you need.
Go in your React Native > Android >app
in the app folder,
you can see a build just delete this folder and Clear React Native project by npm cache clean cmd/Terminal Command.
Now try to run I hope it will Run for some of you.
It's working for me.
I'm trying to set up crashlytics beta app distribution process.
I have two schemes of building develop-variant of our app: rocket:myapp_developDebug and rocket:myapp_developRelease (names slightly changed). I have them both built and located in same output dir.
If I run rocket:crashlyticsUploadDistributionMyapp_developDebug, everything is ok and I see that distribution on Crashlytics Beta page. But for rocket:crashlyticsUploadDistributionMyapp_developRelease it succesfully finishes 'build', but app doesn't get its way to Beta.
From its message Uploading /path/to/project/proj.android-studio/app/build/outputs/apk/rocket-myapp_develop-release.apk to Crashlytics... it's clear that I have that apk; also it is really being uploaded (based on time and network load). The version itself is recognized by Crashlytics (on versions page).
What am I missing?
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.
I need help for removing the beta app submitted in google play store, Recently I have submitted my app with Targeted SDK version 23 for beta testing but now I want to submit the app with targeted SDK version 15 for production.
I have tried by submitting the App to Production with targeted SDK version 15 but it showed me an error saying:
Permission model downgrade PROBLEM: Users that have the APK version
code XXXX1, which targets SDK 23 or higher, will receive an error when
they attempt to upgrade to this apk XXXX2 because it targets SDK 15.
Is there any way to delete the existing beta app or to submit the production app with SDK15 other than un-publishing the app? Un-publishing the app will cause the inconvenience to existing users.
There is no way to delete a build from the Alpha or Beta channels. What you have to do is, deploy an artifact with a higher build code to the channel, then promote the channel to production. The APK that you want to remove will not show up, only the build with the highest build code, so there is no risk to doing this.
(source - just worked with Google Play support on a similar issue.)