Funny, you seem to ask for help but don't want to try the suggestions insisting it's Googles problem and thinking they would solve it...
Looking at your manifest, I think there may be problems regarding screen compatibility mode. See http://developer.android.com/guide/practices/screen-compat-mode.html and http://android-developers.blogspot.de/2011/07/new-mode-for-apps-on-large-screens.html. Now, why does the problem occur without changes to the manifest? Yes, there may have been changes made by Google. However, I would not wait until Google fixes the problem. That's not necessarily Googles strength. It may even be the case that Google does not think it does something wrong. Instead, I would add a supports-screens element and set android:targetSdkVersion<http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#target>. The values you should use depend on your app. I also would use a current sdk version to build the app. Achim Am Mittwoch, 22. Mai 2013 17:56:30 UTC+2 schrieb Julian Bunn: > > Hi Bob ... thanks for the input. I really don't want to set such a high > minSdk as then I would lose many of my >10,000 customers, who are running > older versions of the OS. > > It's been a few days since this tablet problem appeared so I'm going to > check back with those customers to see if the app availability in the Play > Store has changed in the meantime. > > > > On Tuesday, May 21, 2013 7:39:58 AM UTC-7, bob wrote: >> >> I agree that *it probably does not have to do with the 2.2 build*. >> >> I was having the same problem and was using the 2.2 build. >> >> However, I switched from 2.2 to 4.2 SDK, and this did not remedy the >> problem. >> >> However, I was able to "sort of remedy" the problem by setting >> >> minSdkVersion=15 >> targetSdkVersion=15 >> >> You might want to try that as an experiment. >> >> Thanks. >> >> >> On Monday, May 20, 2013 2:15:43 PM UTC-5, jjbunn wrote: >>> >>> I don't think it has anything to do with the 2.2 build (what makes you >>> think it does?) as I already tried a version targeting 4.0 and the result >>> was the same. >>> >>> My users report that there are several other apps in the Play Store that >>> are now marked as incompatible for their tablets, which were compatible a >>> few days ago. >>> >>> So, my impression is that the problem is in the Play Store, but I'd love >>> to be wrong, because then I could fix it myself! >>> >>> Julian >>> >>> >>> On Monday, May 20, 2013 10:41:46 AM UTC-7, Jonathan S wrote: >>>> >>>> Problem is Android 2.2 SDK build. You can built it on 4.0 and keep >>>> minimum API level. Just be very careful. >>>> >>>> On Monday, May 20, 2013 12:50:39 PM UTC-4, jjbunn wrote: >>>>> >>>>> I uploaded a new APK for one of my apps on Friday. There was no change >>>>> to the manifest or build settings for the app, but some of my >>>>> customers using tablets like the Note 10 and Nexus 10 tell me that the >>>>> new APK is marked as incompatible in the Google Play store, whereas >>>>> they were happily using the previous version on those devices. >>>>> >>>>> In my Android Developer Console, the APK is marked as being compatible >>>>> with those tablets (in fact it is marked as compatible with over 2000 >>>>> devices, and incompatible with 0 (zero)). >>>>> >>>>> So I am very puzzled what has happened, and would really appreciate >>>>> some help :-) >>>>> >>>>> Here is the Manifest. I build with the Android 2.2 SDK. >>>>> >>>>> <?xml version="1.0" encoding="utf-8"?> >>>>> <manifest xmlns:android="http://schemas.android.com/apk/res/android"; >>>>> package="com.xxx.xxx.xxx" >>>>> android:installLocation="auto" >>>>> android:versionCode="76" android:versionName="5.9.2"> >>>>> <uses-permission >>>>> android:name="android.permission.RECORD_AUDIO"/> >>>>> <uses-permission >>>>> android:name="android.permission.MODIFY_AUDIO_SETTINGS"/> >>>>> <uses-permission >>>>> android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> >>>>> <uses-sdk android:minSdkVersion="4"/> >>>>> <application android:icon="@drawable/icon" >>>>> android:label="@string/app_name" >>>>> android:theme="@android:style/Theme.NoTitleBar" > >>>>> <activity android:name=".MyApp" >>>>> android:label="@string/app_name"> >>>>> <intent-filter> >>>>> <action android:name="android.intent.action.MAIN" /> >>>>> <category >>>>> android:name="android.intent.category.LAUNCHER" /> >>>>> </intent-filter> >>>>> </activity> >>>>> </application> >>>>> </manifest> >>>>> >>>>> -- -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
