This old chestnut again,
After a lot of searching the best thread I found on this is 'App not Installed' Error on Android
In my case I have checked all the fixes mentioned but still have the problem when I try to install the unsigned APK file.
The app runs fine on my phone when I install it from Eclipse, but when I put it on google drive and then point my phone to the APK I get the error above. I have a Note 1
I have uninstalled the old app, reset my phone etc but no luck. It worked fine for me until today, I would just put the APK on google drive and install it from there and it worked each time, just stopped working today and I have changed nothing.
I have both signed and Unsigned versions of the APK
Here is my manifest file
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.app.nquizitive"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk android:minSdkVersion="8" />
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:resizeable="true"
android:anyDensity="true" />
<uses-permission android:name="android.permission.INTERNET" />
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name" >
<activity
android:name="com.app.nquizitive.StartupActivity"
android:label="#string/app_name" android:screenOrientation="landscape">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
My devices will only load signed APKs under these conditions. It appears to be a case of Google's boot on our neck. So I'm not sure what an unsigned one is good for unless you load it on a $45 USD Google-free device from China. So I release signed ones with increasing version numbers but with version "1" google-wise and then release "1"/"1.0" on Google Play.
Related
I have a Samsung Galaxy SII (Sprint version Epic 4G Touch) running Cyanogen 9 (4.0.4 ICS). Screen density is at default. On the market it says my app is compatible with API 8-16+ and supports screens from small-xtra large. For some reason it is still not compatible with my phone. Does it have to do with my custom rom? or possibly the fact I'm running 4.0.4? All users that cannot install also seem to be running custom roms.
My Manifest:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="org.pwnsro.dayz"
android:versionCode="5"
android:versionName="1.0.4" >
<uses-sdk android:minSdkVersion="8"
android:targetSdkVersion="15" />
<supports-screens
android:anyDensity="true"
android:largeScreens="true"
android:normalScreens="true"
android:resizeable="true"
android:smallScreens="true" >
</supports-screens>
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name" >
<activity
android:name=".DayZActivity"
android:label="#string/app_name"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
Also my project.properties:
target=android-15
*Edit:
It seems only users of AOSP Roms on ICS are having compatibility issues. I switched to a Samsung 4.0.4 rom and I was able to install this from the market.
Do you happen to have copy protection set to ON in android developer console? Have a look at this page.
To copy protect an application, set copy protection to "On" when you configure publishing options for your application. Google Play will not show copy-protected applications on developer devices or unreleased devices.
Since you said this:
I switched to a Samsung 4.0.4 rom and I was able to install this from the market.
I guess that the problem is/was your custom ROM. Have you tried another custom ROM? Maybe it is a problem with that specific ROM or Google Play don't recognize it as a compatible SO.
I recently published my Android app to the market and everything seemed fine.
I tried to download it on a particular phone (Samsung epic 4g (SPH-D700)) and it was not available. It looks like it is being filtered, along with most the other Samsung galaxy s phones.
Should I change something in my manifest so it doesn't become filtered?
Im also trying to search for it on my computer and it doesnt even show up when i do that. Does this mean it didnt actually upload it to the market?
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="send.text.fast"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk android:minSdkVersion="5" />
<uses-permission android:name="android.permission.SEND_SMS"> </uses-permission>
<uses-permission android:name="android.permission.READ_CONTACTS"> </uses-permission>
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name" >
<supports-screens android:smallScreens="true"
android:normalScreens="true" android:largeScreens="true"
android:anyDensity="true">
</supports-screens>
<activity
android:name=".Main"
android:label="#string/app_name"
android:screenOrientation="portrait">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
i'm having the same problem too. the Market (now goes by a different name) has this recently new (long awaited, they claim) feature to filter out apps that are not compatible with your device.
did you try setting minSdkVersion to your phone's particular version? try lowering it. one thing i did not know is that you can set minSdkVersion down but still target a higher version.
my app works on my android phone upon side-loading. but since i've published my app, i still can't find it on my phone when using the Market app. when i go to my app's webpage, i get a little message saying this app is not compatible with your device, which is wrong. of course, my phone has been rooted among other things (i.e. non-stock kernel/roms/launchers/etc...).
the joy of fragmentation.
I have developed an app using PhoneGap and tested the same in different version of emulator and also in my Motorola Photon. I have not faced any problem in testing.
But when I published the same in the market it says "This app is incompatible with all of your devices.". My devices are with different screen size, different OS version ranging from 2.1 to 2.4.
In publish home page, it says "This application is available to over 679 devices." It includes Motorola Photon 4g and all other devices which I have registered in the market download.
I have republished the code many times by updating manifest file and java file based on all the answers given through out the stackoverflow for this kind of issues. To list it,
Removing user-permission
Updating all combinations of supports-screens
Refreshing the save button in the publish page several times
Uninstalling the apps in my mobile (But I have few more devices where I have not tested my apps but still says incompatible)
Running aapt tool
Removing the jar files from lib folder and referring that externally in Eclipse
Few more changes that I cant recall
below is the manifest file
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.test.myapps"
android:versionCode="5" android:versionName="1.4">
<uses-sdk android:minSdkVersion="7" />
<supports-screens android:largeScreens="true"
android:normalScreens="true" android:smallScreens="true"
android:resizeable="true" android:anyDensity="true" />
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.SET_WALLPAPER" />
<uses-permission android:name="android.permission.SEND_SMS"/>
<application android:icon="#drawable/app_icon" android:label="#string/app_name">
<activity android:name="com.test.myapps.HomePage" android:label="#string/app_name">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="com.google.ads.AdActivity"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize">
</activity>
</application>
</manifest>
Please, help me in fixing the same. Thanks in advance....
Did you specifically run "aapt dump badging <.apkfile> ?
Android docs here.
I had a similar problem. Turns out I needed to use in my manifest the
android:required="false" for several uses-features, like:
< uses-feature android:name="android.hardware.telephony" android:required="false" >
Full manifest example here. The results of dump badging showed that the market had added several uses-features (a bit
further down in aapt output) that excluded mostly Samsung devices.
Check if there is any compatibility, you need to start with :
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize">
Are you sure that you were checking the latest version of APK , not the old one. you will need to activate it. not only upload it ..
Users report that my app is not supported on their Droid X phones. The manifest file looks like this:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="xxxx"
android:versionName="1.4"
android:installLocation="auto"
android:versionCode="14">
<uses-sdk android:minSdkVersion="4" />
<uses-configuration android:reqFiveWayNav="false"
android:reqHardKeyboard="false"
android:reqKeyboardType="undefined"
android:reqNavigation="nonav"
android:reqTouchScreen="notouch"></uses-configuration>
<supports-screens android:xlargeScreens="true"
android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true"></supports-screens>
<uses-permission android:name="android.permission.READ_PHONE_STATE"/>
<application android:icon="#drawable/icon" android:label="#string/app_name">
<activity android:label="#string/app_name" android:name=".Main"
android:theme="#android:style/Theme.NoTitleBar.Fullscreen">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
I really do not understand why it is not supported because it's a very simple app and I do not find anything odd in the Manifest file.
Could the fault be on users' phones instead of inside of my app? Any suggestions?
--- EDIT ---
My other apps do not have attributes uses.configuration and supports-screen and they DO NOT produce such error (users did not report any such).
Could the problem be in these attributes?
Some droid phones has this error 18 when installing or updating some apps . It's caused by smdl2tmp . You will see this log line : Failed to create secure container smdl2tmp
The solution is to manually delete smdl2temp1 file.
The file is likely to reside in 2 locations:
/sdcard/.android_secure: this is an invisible folder on your SD card, which you can access with any file manager(No root needed)
/mnt/secure/asec/: access to this folder requires root and a program like root explorer
I hope it would help .
Actually it was a problem in
My other apps do not have attributes uses.configuration and
supports-screen and they DO NOT produce such error (users did not
report any such).
Once I removed these attributes, the app became supported on all devices.
Anyone knows why? I will wait a couple of days before opening a separate topic on this issue and link it here.
Are there any known issues about Samsungs SG2 (2.3.4) concerning the compatibility of Apps. Many potential users of our app with a SG2 report that the Android Webstore thinks the app is not compatible and that the app is not visible on the Android Market App. Whereas the same users are able to install and use the app without any problems if they download the app from Android Pit.
Edit: I have not set a maximum SDK Version. Min SDK-version is 7. According to the developer console there are already some users with SGS2.
Edit2: Here are some parts of the manifest:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="my.app.full" android:installLocation="auto"
android:versionName="1.1" android:versionCode="1">
<uses-sdk android:minSdkVersion="7" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<application android:icon="#drawable/icon" android:label="#string/app_name"
android:name="myAppPlaceholderName">
<!-- Activities left out -->
<receiver android:name="my.app.OnebyOneWidgetProvider">
<intent-filter>
<action android:name="android.appwidget.action.APPWIDGET_UPDATE" />
</intent-filter>
<meta-data android:name="android.appwidget.provider"
android:resource="#xml/one_by_one_widget_info" />
</receiver>
<supports-screens android:anyDensity="true"
android:largeScreens="true" android:smallScreens="true"
android:normalScreens="true" android:xlargeScreens="false" android:resizeable="true" />
</application>
</manifest>
I am also using the deprecated copy protection of androidmarket.