Manifest is malformed when installing app on Android 7 (API 24) - android

I have an Android app that would not install on a Samsung S6 running Android 7. It would not install both from the Play Store and directly from Android Studio deployment.
I checked logcat and it stated that I have a package/class listed in my manifest as Managers.MyApp. I indeed had a folder named Managers and so files in there used the same name for their package.
I renamed the folder plus all references to managers (lowercase m). I did a global search to make sure there were no remnants. The app was finally successfully deploying to the Android 7 Samsung S6.
I uploaded the app to Internal Testing in Play Console (where the Samsung device would previously also fail to install the app from, with the same error). This time it was able to install from internal testing, so surely all is well with the app.
However, when I released the app to production, the Samsung device is again unable to install the app, showing the same error as before: Malformed manifest, invalid class: Managers.MyApp.
I do not have any instances of Managers anymore with an uppercase m. I checked the manifest and it certainly has managers.MyApp.
Is there some caching going on with Play Console? Or are there extra steps I need to implement. MyApp is a class that extends Application.

Related

React native app-release build not working for some android devices

I gave a build for android using gradlew assembleRelease.
but app-release.apk file not working for some devices like honor 9i, Redmi note 5 pro.
Make sure your app is compatible with OS of your device. Enable installation from unknown sources. Sign your app before sending .apk. It is important due to security restriction of some devices.
signing your app
Happened to me on some devices as well. Even if you allow installation from unknown sources turned on. Some devices alter the final .apk file (maybe for security reasons). So we used android playstore publish for distributing app as test/beta builds. Pick one appropriate for your pre release distro. It should work fine.

Android third party causes "app not installed" error

I have created with the use of android studio a small project and then I generated the signed apk. Then I tried to install it in three phones and in the first one (which has android 8) the app was installed successfully but in the second one (which has android 4.2) and third one (which has android 5) I got the "app not installed" error. This is my second app (project) and my first one has been installed successfully in all these three phones. The minimum SDK version of the app is Android 4.0.3 (API level 15), so that's not causing the problem. Can anyone guess where the problem is?
Sign the apk with both v1 and v2 signatures. this is the most likely culprit given your scenario. apk will not get installed on devices with less than marshmallow if you only sign with v2
Well you can try following:
Change install location of app on the phones it's creating problem.
Try resetting app preferences
Clear Data and Cache of Package Installer
Allow Apps from Unknown Sources (Go to Settings → Security → Unknown Sources. Enable Unknown Sources. And then try installing App)
Try Deleting .android_secure/smdl2tmpl.asec file from your SD Card if using SD card
Resign the app.
Try changing app codes by using some apk editor app

Unable to open file alpha.apk You do not have an app installed on this device

I am trying to build android apk file via cordova build android. It gives me an apk at the location of
D:/wamp/www/templateproject/platforms/android/build/outputs/apk/android-debug.apk
When I try to open that app in my mobile i get this alert message.
Unable to open file android-debug.apk. You do not have an app installed on this device to open this type of file.
Note: I have already check the installation from unknown sources.
How do I open such file ?
Note: It seems working with my friend device Redmi note 3 but not working with my device Redmi note 4 and moto g2 not sure what is the issue.
The problem is with the updated skype. I was trying to share the apk file via desktop skype to android skype. With the latest update on skype it was not allowing me to open apk file. Bug with the skype. However the file is working fine if I try to access it from file manager.
The reason Redmi note 3 was working because it had skype of older version and other two mobile like redmi note 4 and moto g2 had updated one.

Failed to install app apk in android device

I have the app running fine in the android emulator. But when I tried to install in the device it is giving error.
In CoolPad Note - running 5.1 version - error is "Failed to install the app"
In Galaxy A7 - running 6.0 version - error is "parsing failed"
I am using sqlite db, apache csv parser lib, Square's sqldelight.
Min Sdk - 19 and Max Sdk - 25
I tried giving all the uses-permission based on this link
I unlocked developer options in the phone and enabled installing from unknown sources. Still not able to install the app. In the same phone, I can install a simple android app. So the problem is with the package or the code. Please help.
Usb with both the phones are not working. So I am sending the apk through bluetooth and then installing it with package installer in the phone. How to get the installation log from the phone.
The app is 4 forms and uses fragments. If needed I can upload the apk.
I have had a similar problem. For me the problem was the APK Signature Scheme v2 option in Android Studio (version 2.3.1):
https://developer.android.com/about/versions/nougat/android-7.0.html#apk_signature_v2
When signing my apk with Signature version v2 selected, I was able to download and install my apk on a LG Nexus 5X (android 7.1.1). But on a Motorola Moto G3 (android 5.1) I would see "failed to install".
By selecting both signature version v1 and v2 when signing my app, this problem was resolved and I could download and install the apk on both phones.
I hope this will help you and others with the same issue.
If you use Galaxy A7.
You can tap *#9900# in dialer app (name is 'phone').
You can find "RUN DUMPSTATE/LOGCAT" and tap it.
Then tap "COPY TO SDCARD(INCLUDE CP RAMDUMP)".
You can find 'log' folder in MyFiles app.

error code during application install -24 on Rooted device from Google Play Store

I am trying to install the App from Google Play Store. Gets downloaded and fails during installation with:
unknown error code during application install -24
The Same Application got installed with different certificate during debug runs from Android Studio. Now it is not getting deleted or over written. How can i clear the cache completely?
Connected the Mobile using USB and tried to run debug from Android Studio. I get following error on debug run APK transfer.
Failure [INSTALL_FAILED_UID_CHANGED]
Deleting the app through Terminal using adb shell command helped in one of the mobile.
In other mobile, even adb shell command did not work out.
Resetting mobile to Factory setting as final solution helped.
PS: Please voteup if you find this helpful.Thanks
Check manifest file and compare with previous one.
If your manifest file contain android:sharedUserId in previous version and it is absent in current version then this error will occured.
Solution is uninstall it and install fresh copy.
The main cause of Google Play Store Error Unknown Error Code During Application Install: 24 is cache problem. However, it can arise at different aspects as listed below:
It can be due to Google Play Store Cache and Data problem.
It can arise due to unwanted junk and residue files.
This error can also appear if you are trying to install an app which was earlier installed in your phone and was uninstalled but all the files of the app was not deleted from your phone.
It can also be caused if your internal storage is full.
Depending on the causes, there are 5 Solutions to Fix Google Play Store Error Unknown Error Code During Application Install: 24. They are listed below:
Solution 1 – Restart your Android Phone.
Solution 2 – Clear Cache and Data of Google Play Store, Google Service Framework and Download Manager.
Solution 3 – Remove Junk files from your internal storage.
Solution 4 – Check if you have sufficient memory in your internal storage.
Solution 5 – Factory Reset your Android Phone.

Categories

Resources