Hi, i also have the suspicion that the carriers filter out certain apps based on the requested permission. I have a app that requests permission for RECORD_AUDIO, and since i use admob i also need INTERNET and ACCESS_COARSE_LOCATION.
And with request for RECORD_AUDIO permission i can't see my app in the "newest" list but as soon as i remove the permission it shows up. However, I can always search for the name of the app and find it, even if it would not show up in the "newest" list. My explanation would be that either google or the carriers filter out completely or partly apps that either would be suitable for voip calls ( INTERNET + RECORD_AUDIO ) or in your case just plain phone apps (CALL_PHONE) - but could just be the regular paranoia ;) ~Peter On 9 Sep., 04:02, Lance Nanek <[email protected]> wrote: > The version of aapt you are using, from Android 2.1, appears to be too > old to show the uses-feature entries, by the way. Example: > > $ platforms/android-8/tools/aapt dump badging test.apk > package: name='com.mytest' versionCode='1' versionName='1.0' > application: label='myTest' icon='res/drawable-mdpi/icon.png' > launchable activity name='com.mytest.MyTest'label='myTest' icon='' > uses-permission:'android.permission.READ_CONTACTS' > uses-permission:'android.permission.INTERNET' > uses-permission:'android.permission.ACCESS_NETWORK_STATE' > uses-permission:'android.permission.ACCESS_COARSE_LOCATION' > uses-permission:'android.permission.ACCESS_COARSE_UPDATES' > uses-permission:'android.permission.READ_PHONE_STATE' > uses-permission:'android.permission.CALL_PHONE' > sdkVersion:'4' > targetSdkVersion:'8' > uses-feature:'android.hardware.location' > uses-feature:'android.hardware.location.network' > uses-feature:'android.hardware.telephony' > uses-feature:'android.hardware.touchscreen' > main > supports-screens: 'small' 'normal' 'large' > locales: '--_--' > densities: '120' '160' '240' > > $ platforms/android-7/tools/aapt dump badging test.apk > package: name='com.mytest' versionCode='1' versionName='1.0' > application: label='myTest' icon='res/drawable-mdpi/icon.png' > launchable activity name='com.mytest.MyTest'label='myTest' icon='' > uses-permission:'android.permission.READ_CONTACTS' > uses-permission:'android.permission.INTERNET' > uses-permission:'android.permission.ACCESS_NETWORK_STATE' > uses-permission:'android.permission.ACCESS_COARSE_LOCATION' > uses-permission:'android.permission.ACCESS_COARSE_UPDATES' > uses-permission:'android.permission.READ_PHONE_STATE' > uses-permission:'android.permission.CALL_PHONE' > sdkVersion:'4' > targetSdkVersion:'8' > main > supports-screens: 'small' 'normal' 'large' > locales: '--_--' > densities: '120' '160' '240' > > They don't look particularly relevant in this case anyway, but just so > you know in the future. I suppose maybe it could matter here if > carriers are capable of specifying the Market shouldn't show things > like telephony apps on devices on their network and some did so and > some didn't? > > On Sep 3, 8:04 pm, Gustavo <[email protected]> wrote: > > > > > Thanks for the quick reply Lance, > > > So I read that post and seems that my app is perfectly fine. > > > gust...@gustavo-desktop:/opt/android/platforms/android-2.1/tools$ ./ > > aapt dump badging /home/gustavo/android_app/test_app.apk > > package: name='com.test.android' versionCode='1' versionName='1.0' > > application: label='Test' icon='res/drawable-mdpi/icon.png' > > launchable activity name='com.test.android.MainActivity'label='' > > icon='' > > uses-permission:'android.permission.ACCESS_COARSE_UPDATES' > > uses-permission:'android.permission.READ_PHONE_STATE' > > uses-permission:'android.permission.CALL_PHONE' > > uses-permission:'android.permission.INTERNET' > > uses-permission:'android.permission.ACCESS_NETWORK_STATE' > > uses-permission:'android.permission.ACCESS_COARSE_LOCATION' > > uses-permission:'android.permission.READ_CONTACTS' > > sdkVersion:'4' > > main > > other-activities > > other-services > > supports-screens: 'small' 'normal' 'large' > > locales: '--_--' > > densities: '120' '160' '240' > > > I don't think there's nothing wrong with it. > > > manifest.xml: > > > <uses-permission > > android:name="android.permission.ACCESS_COARSE_UPDATES" > > android:required="false"/> > > <uses-permission android:name="android.permission.READ_PHONE_STATE" > > android:required="false"/> > > <uses-permission android:name="android.permission.CALL_PHONE" > > android:required="true"/> > > <uses-permission android:name="android.permission.INTERNET" > > android:required="true"/> > > <uses-permission > > android:name="android.permission.ACCESS_NETWORK_STATE" > > android:required="false"/> > > <uses-permission > > android:name="android.permission.ACCESS_COARSE_LOCATION" > > android:required="false" /> > > <uses-permission android:name="android.permission.READ_CONTACTS" > > android:required="false" /> > > > <supports-screens android:largeScreens="true" > > android:normalScreens="true" android:smallScreens="true" > > android:anyDensity="true" /> > > > <uses-sdk android:minSdkVersion="4" /> > > > default.properties: > > target=android-8 > > > I really don't understand what's going on with just a simple > > publishing... and this is not even the first time I'm doing this =( > > > Any other ideas? > > > - Gus > > > On Sep 3, 8:19 pm, Lance Nanek <[email protected]> wrote: > > > > Two other things you can check are if you enabled copy protection, and > > > if any uses-feature entries are getting added for you by the build > > > tools. There's a aapt dump badging command you can run to check the > > > latter:http://android-developers.blogspot.com/2010/06/future-proofing-your-a... > > > > On Sep 3, 4:31 pm, Gustavo <[email protected]> wrote: > > > > > Hi guys, > > > > > I've just published my app on the android market but something weird > > > > happened, this is not my first time publishing an app so I'm almost > > > > sure I'm not doing anything wrong here, so would like to know if > > > > anyone had this same issue before. > > > > > 1st Attempt: > > > > > Manifest.xml file > > > > > <supports-screens android:largeScreens="true" > > > > android:normalScreens="true" android:smallScreens="true" > > > > android:anyDensity="true" /> > > > > > <uses-sdk android:minSdkVersion="4" /> > > > > > default.properties: > > > > > # Indicates whether an apk should be generated for each density. > > > > split.density=false > > > > # Project target. > > > > target=android-4 > > > > > 2nd Attempt: > > > > > Manifest.xml file > > > > > <supports-screens android:largeScreens="true" > > > > android:normalScreens="true" android:smallScreens="true" > > > > android:anyDensity="true" /> > > > > <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="8" /> > > > > > default.properties: > > > > > # Indicates whether an apk should be generated for each density. > > > > split.density=false > > > > # Project target. > > > > target=android-8 > > > > > This is suppose to be visible for all android devices that has the > > > > version 1.6 and later, right? we have 3 androids here and I can only > > > > see the app in the android market with the 1.6 android phone, the > > > > other ones are 2.0.1 and 2.01 and I'm not being able to see the app > > > > there. > > > > > Is there anything wrong with this configurations or something is > > > > really going on with apps publication lately? > > > > > Thanks you very much, > > > > > - Gus -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
