I contacted Google, and they looked into the issue. There were a
combination of issues. First, they said that the switch to the new
Developer Console played a part because the old developer console was more
lenient. They said that my old manifest file worked in the old Devloper
Console, but
Hi Fredrik,
I have posted an answer to this problem. Check it out when you get a
chance, and it should resolve your problem.
-Michael
On Wednesday, May 22, 2013 8:29:05 AM UTC-7, Fredrik Hyttnäs-Lenngren wrote:
I have the same issue, two of my apps claims to not be supported on the
I have the same issue, two of my apps claims to not be supported on the Nexus
10 on Google Play. According to the developer console the Nexus 10 is
supported. This happened when I published an update last week, nothing was
changed in the manifest (other than version code/number).
--
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
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
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,
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
7 matches
Mail list logo
