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.
