I am trying to upload an update to google play store but after uploading the apk it says 0 supported device.
Some of the similar questions are caused by 3rd party libraries but i don't use any new library.
I am using v7 appcompat support library. I was using v4 previously and it had no problem with Google Play. I don't know if this is the problem but this is the only change i made in terms of external libraries.
Here is my manifest file :
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.saliherikci.poemnotebook"
android:versionCode="10"
android:versionName="2.0" >
<uses-sdk
android:minSdkVersion="8"
android:targetSdkVersion="25" />
<application
android:allowBackup="true"
android:icon="#mipmap/ic_launcher"
android:label="#string/app_name"
android:logo="#drawable/ic_action_logo"
android:theme="#style/AppTheme" >
<activity
android:name="com.saliherikci.poemnotebook.MainActivity"
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.saliherikci.poemnotebook.ReadPoemActivity"
android:label="#string/title_activity_read_poem" >
</activity>
<activity
android:name="com.saliherikci.poemnotebook.SelectedAuthorsPoemsActivity"
android:label="#string/title_activity_selected_authors_poems"
android:parentActivityName="com.saliherikci.poemnotebook.MainActivity" >
<meta-data
android:name="android.support.PARENT_ACTIVITY"
android:value="com.saliherikci.poemnotebook.MainActivity" />
</activity>
<activity
android:name="com.saliherikci.poemnotebook.FavouritesActivity"
android:label="#string/title_activity_favourites"
android:parentActivityName="com.saliherikci.poemnotebook.MainActivity" >
<meta-data
android:name="android.support.PARENT_ACTIVITY"
android:value="com.saliherikci.poemnotebook.MainActivity" />
</activity>
</application>
</manifest>
I wonder what might be the problem.
I ran into the same thing last night and read the most recent articles on this and I guess there is a recent Google bug causing the supported devices to always show up as 0 until it's actually rolled out to production.
I took a chance and released the update and sure enough all the supported devices were there in production. So if you haven't changed anything in the Manifest from the last release you're probably safe to do so as well. (Also I don't see anything in the posted Manifest that would cause any issues)
Related
I am trying to update my application since yesterday (5/3/14) but i can not. I added a higher version code and a higher version number than the previous application but nothing happened. This screenshots shows my problem.
What can i do?
Let me show you my AndroidManifest.xml too:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package=""
android:versionCode="19"
android:versionName="3" >
<uses-sdk
android:minSdkVersion="9"
android:targetSdkVersion="19" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.VIBRATE"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<application
android:allowBackup="true"
android:icon="#drawable/ic_launcher"
android:label="#string/app_name">
<receiver android:name="MyWidgetProvider" >
<intent-filter >
<action
android:name="android.appwidget.action.APPWIDGET_UPDATE" />
</intent-filter>
<meta-data
android:name="android.appwidget.provider"
android:resource="#xml/widget" />
</receiver>
<receiver android:name="MyWidgetProvider2" >
<intent-filter >
<action
android:name="android.appwidget.action.APPWIDGET_UPDATE" />
</intent-filter>
<meta-data
android:name="android.appwidget.provider"
android:resource="#xml/widget2" />
</receiver>
<receiver android:name="MyWidgetProvider3" >
<intent-filter >
<action
android:name="android.appwidget.action.APPWIDGET_UPDATE" />
</intent-filter>
<meta-data
android:name="android.appwidget.provider"
android:resource="#xml/widget3" />
</receiver>
<meta-data android:name="com.google.android.gms.version"
android:value="#integer/google_play_services_version"/>
<activity
android:name="gr.backatel.rootchecker.RootChecker"
android:configChanges="orientation|keyboardHidden|screenSize"
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.android.gms.ads.AdActivity"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize" />
<activity android:name=".stage1" android:label="Check for Root"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize">
</activity>
<activity android:name=".moreinfo" android:label="#string/info">
</activity>
<activity android:name=".settings" android:label="Themes">
</activity>
</application>
</manifest>
When i am trying to update my app!!
Using mobile browser:
Screeshot : on Mozilla
Screenshot on Chrome:
When progress is 99% nothing happens in the end.
Using mobile shows the error that upload failed
I tried to sing out and sign back but nothing changed.
Thanks in advance!! :)
just log out and back in or use firefox instead of chrome. That should actually solve your problem...
I can now confirm that there is an issue uploading applications at the moment, there are a lot of people having issues, Google are looking into it now, and it should be fixed shortly.
try recompiling your app.
After that, clean the cache of the browser. Try using a different browser if nothing has changed
Try to add android:debuggable="false" inside <application> tag
Some things you can try:
Unpublish your app, wait for a while, upload your apk, then republish the app.
Use a different connection or a system, if that is what the problem is.
Add one of your friend OR another email of yours as a release manager and try uploading from his id.
Clear your browser cache, cookies, temp files etc and retry.
Just use a different name for the APK.
Do let me know if any of these work.
Upload for beta testing. After you have successfully downloaded your app from beta and you are certain it works correctly publish to production. See Beta testing and staged rollouts for details.
As far as I am aware google play services are fine, I uploaded an APK not too long ago and it all went okay, but that being said there could always be an issue with the google servers, however here are a few things you can try.
Examine your project by using Android Lint tool for any omissions and errors. To find out about lint see this link:
http://tools.android.com/tips/lint
Also, you could use the aapt tool, included in the Android SDK, to process your application, based on its declared features and permissions. To do so, run aapt with the dump badging command. It will parse your application's manifest and apply the same rules as used by Google Play to determine the features that your application requires. You can view more on this here:
http://developer.android.com/guide/topics/manifest/uses-feature-element.html#testing
I have built & sign my apk by Eclipse ADT as it is describes (export and sign by creating a new key). But it can't be install on real device while an errors occurs, such as "installer package error". I have no Android device & sent my apk to friends by email. I'm using AVD and everyth is fine with it. Any suggestions? Thanx guys.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.XXXX.YYYY"
android:versionCode="0"
android:versionName="0.9.2" android:installLocation="internalOnly">
<uses-sdk
android:minSdkVersion="13"
android:targetSdkVersion="17" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name"
android:theme="#style/AppTheme"
android:hardwareAccelerated="true"
android:permission="android.permission.INTERNET"
android:allowBackup="true">
<activity
android:name="com.XXXX.YYYY.ActivityMain"
android:label="#string/main_activity_title"
android:launchMode="singleTop" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name="com.XXXX.YYYY.ActivityDetails"
android:parentActivityName="com.XXXX.YYYY.ActivityMain"
android:excludeFromRecents="true"
android:configChanges="orientation|screenSize">
</activity>
</application></manifest>
UPD: apk installs good, but the error occurs if choose Open (see screenshot). After that app works fine. But on tablet if try open app it says "App deleted".
UPD2: add supporting API 4+ meta tag for the 2nd activity, but it takes no effect
<meta-data
android:name="android.support.PARENT_ACTIVITY"
android:value="com.XXXX.YYYY.ActivityMain" />
You probably need to make sure your device and your friend's devices can install apps that are not from the play store.
This is a feature you have to specifically set, or else apps that are outside the play store will not install.
Here is how to set it:
Open settings
Find the Security settings (Pre 4.0 it is under Applications)
Look for a setting that says Unknown sources, or non-market apps
Enable that setting
Everything should work after that!
Here is an article with pictures if you are still confused :)
Your example was missing the closing </manifest> and android:enabled. I'm not sure if the latter would prevent a device from fully installing it but the first one would.
I've also had issues using the full activity names in the past, so you may want to try using simplifying them to see if it helps.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.XXXX.YYYY"
android:versionCode="0"
android:versionName="0.9.2" android:installLocation="internalOnly">
<uses-sdk
android:minSdkVersion="13"
android:targetSdkVersion="17" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name"
android:theme="#style/AppTheme"
android:hardwareAccelerated="true"
android:allowBackup="true">
<activity
android:name=".ActivityMain"
android:label="#string/main_activity_title"
android:enabled="true"
android:permission="android.permission.INTERNET"
android:launchMode="singleTop" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity android:name=".ActivityDetails"
android:parentActivityName=".ActivityMain"
android:excludeFromRecents="true"
android:configChanges="orientation|screenSize">
</activity>
</application>
</manifest>
Is "Unknown sources" option under "security" allowed on device?
My problem was a duplicate internet permission request on Manifest! When I remove that from activity app was run normally.
I'm developing a game on Android that has been running well over months on all devices I know of. But recently I noticed that S4 users typically uninstall the app right away, and finally someone with an S4 (jflte) wrote a review, stating that the app "does not start".
I cannot reproduce this behaviour in an AVD (related) and won't have an S4 at hand any time soon. Googling the issue, I found that this is not umcommon with S4's and might be related to SD-card installs. I did not find any solution though. My app uses OpenGL with android.opengl.GLSurfaceView.
Question is: What are my options to investigate the problem? I've seen the RTL option, but it seems to be some kind of premium thing. Disabling S4 support in the Play Store does not count as solution. I would love to have LogCat output of the startup attempts on an S4.
Here's my AndroidManifest, as far as relevant:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="app.orbs"
android:versionCode="24"
android:versionName="2.1"
android:installLocation="auto" >
<uses-sdk
android:minSdkVersion="7"
android:targetSdkVersion="18" />
<application
android:allowBackup="true"
android:icon="#drawable/orb_launcher"
android:label="#string/app_name"
android:name="orbs.OrbsApplication">
<activity
android:name="orbs.controller.MainMenuActivity"
android:screenOrientation="portrait"
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="orbs.controller.GameActivity"
android:screenOrientation="portrait"
android:label="#string/app_name" >
</activity>
<activity
android:name="orbs.SettingsActivity"
android:label="#string/app_name"
android:theme="#android:style/Theme.NoTitleBar" >
<intent-filter>
<category android:name="android.intent.category.PREFERENCE" />
</intent-filter>
</activity>
</application>
Thanks in advance!
First thing is to try and get users to send error reports when a crash happens, but lets face it, most people won't do that.
So I would suggest looking into an automatic crash reporting system such as Crittercism.
I have published a new update of my App. After publishing it got a warning like "Warning: Your active APK supports less devices then the previous APK. Some users won't get the update."
So i've compared the details of the current and the prior APK. There is only one difference: The new one has the additional entry "Native Platform: simple-xml.2.6.9.jar".
Do you think that there is a problem with it? Acutally i've intergrated the .jar into my android project.
Additionally, the developer console shows me that the app is now compatible with 0 devices... if i search for a certain device i get a notice that it's because of my manifest settings.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="edu.kit.aifb.nukit"
android:versionCode="8"
android:versionName="#string/app_versionName" >
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.VIBRATE"/>
<uses-sdk
android:minSdkVersion="7"
android:targetSdkVersion="17" />
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name"
android:theme="#style/Theme.KIT.Styled"
android:allowBackup="true" >
<activity
android:name="edu.kit.aifb.nukit.gui.SplashScreenActivity"
android:label="#string/app_name"
android:screenOrientation="portrait"
android:theme="#style/Theme.Sherlock.Light.NoActionBar"
android:clearTaskOnLaunch="true" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity
android:name="edu.kit.aifb.nukit.gui.ChooseCourseActivity"
android:screenOrientation="portrait"></activity>
<activity
android:name="edu.kit.aifb.nukit.gui.QuestioningAndVotingActivity"
android:screenOrientation="portrait"
android:windowSoftInputMode="stateHidden"></activity>
<activity
android:name="edu.kit.aifb.nukit.gui.AnswerQuestionActivity"
android:screenOrientation="portrait"></activity>
<activity
android:name="edu.kit.aifb.nukit.gui.ShowResultsActivity"
android:screenOrientation="portrait"></activity>
<activity
android:name="edu.kit.aifb.nukit.gui.ImpressumActivity"
android:screenOrientation="portrait"></activity>
<activity
android:name="edu.kit.aifb.nukit.gui.LicensesActivity"
android:screenOrientation="portrait"
android:hardwareAccelerated="false"></activity>
<activity
android:name="edu.kit.aifb.nukit.gui.survey.SurveyListActivity"
android:screenOrientation="portrait"></activity>
<activity
android:name="edu.kit.aifb.nukit.gui.survey.QuestionActivity"
android:screenOrientation="portrait"
android:parentActivityName=".SurveyListActivity" >
<meta-data
android:name="android.support.PARENT_ACTIVITY"
android:value=".SurveyListActivity" />
</activity>
<activity
android:name="edu.kit.aifb.nukit.gui.survey.SurveyResultsActivity"
android:label="SurveyResultsActivity"
android:parentActivityName=".SurveyListActivity">
<meta-data
android:name="android.support.PARENT_ACTIVITY"
android:value=".SurveyListActivity" />
</activity>
</application>
if i install the apk directly on my device, it works fine.
This should probably be due to changes done in your Android Manifest relating to max and min sdk versions
<uses-sdk android:minSdkVersion="integer"
android:targetSdkVersion="integer"
android:maxSdkVersion="integer" />
If this SDK version range has been altered, your new updated app might support lesser number of devices.
Alright, i fixed it.
The problem was that actualy only the SurveyLib.jar is using simple-xml-2.6.9.jar and the simplexml.jar was included within the SurveyLib.jar. So i think there was a problem dexing the simplexml.jar within surveylib.jar.
i've created the surveylib.jar again without simplexml.jar but included the simplexml.jar to the libs folder of my app.
now it works fine. thanks to you all for your help.
I developed an android app. Its manifest is very simple and copied below.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.siddjain.jainaartis"
android:versionCode="1"
android:versionName="1" >
<uses-sdk android:minSdkVersion="7" />
<uses-configuration android:reqFiveWayNav="true" />
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name" >
<activity
android:name=".Main"
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=".DisplayForm"
class=".Aarti" >
</activity>
</application>
</manifest>
The Play store reports this app to be incompatible with many devices. Specifically, it reports it to be incompatible with Samsung GT-S5570 which is my phone. I installed the app onto my phone manually, and it works.
The developer console gives this message:
This application is only available to devices with these features, as defined in your application manifest.
Screen layouts: SMALL NORMAL LARGE XLARGE
Required device features
android.hardware.touchscreen
This application is available to over 266 devices.
The device availability dialog lists Samsung GT-S5570 as incompatible.
How can I fix the compatibility issue? What is there in my manifest that is causing the app to be classified as incompatible with Samsung GT-S5570? As mentioned earlier, I have checked the app works on my phone.
The specs of the phone are available here btw. It has a display resolution of 240x320 pixels and has Froyo (android v2.2.1)
Was able to fix this using following manifest (support for small screens has to be declared explicitly). The number of devices to which the app is available increased from 266 to 1272.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.siddjain.jainaartis"
android:versionCode="3"
android:versionName="1" >
<uses-sdk android:minSdkVersion="7" />
<supports-screens android:smallScreens="true"
android:normalScreens="true"
android:largeScreens="true"/>
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name" >
<activity
android:name=".Main"
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=".DisplayForm"
class=".Aarti" >
</activity>
</application>
</manifest>
Might be a carrier restriction. The play store filters apps via known information about your device (screen size, OS, carrier), but not if it can install and/or work or not. It would be a nightmare for development (and non play store apps) if you couldn't install because it checked compatibility.
How long ago did you add the app? If you just added it, it takes several hours for it to propagate and become available.
I see it uses 5 way nav. Does your application use this (I assume so) and does it work in your application?