I added the *android:targetSdkVersion *with a value higher or equal to 11 to my manifest file and uploading it to the developer console. The apk "details" now highlights *"xlarge" * as a new feature. Going to publish the update and see if it REALLY did it or if it's just the Developer Console fooling me.
// Fredrik On Thursday, 23 May 2013 17:50:41 UTC+2, jjbunn wrote: > > Hi Fredrik, > > I'm also having the same problem as OP. Nothing changed in my Manifest, or > build procedure, but now Google Play marks my app as incompatible with e.g. > the Nexus 10. > > It would be really nice if there was some way of asking Google directly if > they have changed something, rather than us all speculating on what might > have happened or what the fix might be :-) > > If I browse the APK in the dev. console I see the following. (I'm not sure > what this information means precisely - I've never looked at it before!) > > "Previously active APKs supported more devices than those in the draft > configuration. Some devices will not receive upgrades. Less > > - Devices currently running *version 76* are no longer supported by > the current configuration. Such devices will not receive upgrades. > *API levels* = 4 and > *Screen layouts* containing any of [small, normal, large, xlarge*] and > *Features* containing all of [android.hardware.MICROPHONE, > android.hardware.TOUCHSCREEN] > - Devices currently running *version 13* are no longer supported by > the current configuration. Such devices will not receive upgrades. > *API levels* = 3 and > *Screen layouts* containing any of [normal, large*, xlarge*] and > *Features* containing all of [android.hardware.MICROPHONE, > android.hardware.TOUCHSCREEN]" > > Julian > > On Thursday, May 23, 2013 2:35:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote: >> >> I actually see now that when I browse the APK in the developer console to >> read the details about it, that it claims that it only supports >> 3-screen-layout, rather than 4 (xlarge missing). >> It should be possible to tinker with the manifest and upload a new apk, >> look at the details and verify what does the trick instead of uploading - >> publish - wait - check - repeat... >> >> // Fredrik >> >> On Thursday, 23 May 2013 09:21:09 UTC+2, Fredrik Hyttnäs-Lenngren wrote: >>> >>> Did you update the apps My Anchor Watch Free" and "My Anchor Watch Pro" >>> or did they just suddenly become "incompatible"? >>> I'm looking towards adding the *android:targetSdkVersion *to one of my >>> apps and release it and see if it works. >>> >>> This is exactly the issue Google had with the Hangout app not being >>> compatible with tables once they update it from Talk, so they must have >>> been caught by surprise as well. >>> >>> Fredrik >>> >>> On Thursday, 23 May 2013 08:54:52 UTC+2, Terry wrote: >>>> >>>> I don't think that *android:**minSdkVersion or ** >>>> android:targetSdkVersion *has anything to do with it. Some of my apps >>>> which are now shown as "incompatible" *and *some which are still >>>> "compatible", *both *only have the *android:**minSdkVersion *in the >>>> AndroidManifest file. >>>> >>>> Two of my apps which were shown in the Play Store as "compatible" only >>>> a few days aga, but which are now shown as "incompatible" (with e.g. >>>> GT-P7500) are "My Anchor Watch Free" and "My Anchor Watch Pro". They are >>>> both listed as compatible (with this particular device) in the Developer's >>>> Console. >>>> >>>> Terry >>>> >>>> >>>> On Wednesday, May 22, 2013 7:15:57 PM UTC+2, Fredrik Hyttnäs-Lenngren >>>> wrote: >>>>> >>>>> I published a completely new app at the same time I published the >>>>> updates, and it shows up on Google Play for all devices. >>>>> Only difference I can see between them is that the new app has the * >>>>> android:targetSdkVersion* included within the *uses-sdk *tag while >>>>> the others only have the *android:minSdkVersion. * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> >>>>> On Wednesday, 22 May 2013 18:42:05 UTC+2, Terry wrote: >>>>>> >>>>>> I have not found a common denominator yet. Strangely enough, those of >>>>>> my apps which are suddenly "incompatible" with the GT-P7500, (according >>>>>> to >>>>>> Play Store), are listed as compatible with the same device in the >>>>>> Developers Console. So it seems pretty obvious that something on Play >>>>>> Store >>>>>> has been broken. >>>>>> Terry >>>>>> >>>>> -- -- 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.
