I have a 0 in front of the version code because that's what Google recommends for what I'm doing: http://developer.android.com/google/play/publishing/multiple-apks.html
Why would CHECK_LICENSE look fishy? You need that there if you are utilizing the Licensing Framework, which I am. And yes, items such as my_package and <more activities> were abstracted out. Note that the Manifest file is the exact same as the previous version of the app where Tablet users were able to find the app, with the only difference being the version code. On Monday, April 1, 2013 12:41:30 PM UTC-7, bob wrote: > > Why would you have a version code that starts with a 0? (i.e. *0400921*) > > The only other thing that looks fishy is com.android.vending.CHECK_LICENSE. > > (assuming your package name isn't really *my_package*) > > Thanks. > > > > > > On Monday, April 1, 2013 11:02:07 AM UTC-5, miketra wrote: >> >> Thanks for the suggestion Richard. I moved the uses-sdk element above the >> <application> node, AND I removed the <supports-screens> node as well and >> re-posted the app, but I still see the same message when I link directly to >> the app in Google Play. And this is after I've loaded the app directly onto >> the tablet myself and it works fine. Unfortunately I've got users who are >> uninstalling the previous version of the app with hopes that this will >> allow their device to get the latest update, and then when it doesn't show >> up still those users are now unable to have the app at all, so I really >> need to get this resolved. Those users told me after the fact, as I >> definitely would not have recommend that strategy. >> >> On Sunday, March 31, 2013 7:43:57 PM UTC-7, RichardC wrote: >>> >>> There has been an odd post or two in the adt-dev group regarding the >>> ordering of elements in the manifest (although I can't find anything in the >>> official docs). >>> >>> So with that said ... I think you should try putting >>> <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="8" /> >>> before the <application> node. >>> >>> I see that someone has already mentioned the <supports-screens> element >>> on SO. >>> >>> On Monday, April 1, 2013 3:15:05 AM UTC+1, miketra wrote: >>>> >>>> My app has been successfully downloaded by tablet users over the last >>>> year without problems. I made an update a week ago, but the only thing >>>> changed in the Manifest file was the app version number and version >>>> string. >>>> After making that update, users are no longer able to access the app in >>>> Google Play. I have an Asus Transformer tablet. I am able to load the app >>>> onto my tablet with no problem. On the tablet, the app won't even appear >>>> in >>>> Google Play unless I search for it on the internet, then link directly to >>>> the app in Google Play. When I do this, Google Play says "your device >>>> isn't >>>> compatible with this version" even though I loaded the app directly onto >>>> the tablet myself. Note that in the Android Developer Console, it says >>>> that >>>> 2600+ devices are compatible, and it says 0 devices are excluded. I looked >>>> at the individual list of devices, and my tablet is listed there as being >>>> compatible. What's the problem, and how do I fix it? To see the Manifest >>>> file, go here: >>>> http://stackoverflow.com/questions/15733070/why-is-app-not-compatible-with-tablets-after-update >>>> >>>> Thanks, >>>> >>>> -Michael >>>> >>> -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com 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 android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
