This is not what I'm seeing.
I'm writing a new app which has never been published or in draft.
I have two devices. One (N1, running 2.2), I'm logged into my main
Google account (which has the Developer account). The other (Hero
running 2.1-update1) is a test account I use (no developer account).
Can anyone else confirm this please?
On Aug 20, 11:27 am, Mark Carter wrote:
> This is not what I'm seeing.
>
> I'm writing a new app which has never been published or in draft.
>
> I have two devices. One (N1, running 2.2), I'm logged into my main
> Google account (which has the Developer accoun
no one noticed the same problem using LVL?
should I ask directly to google? Is this a bug with my account?
On Aug 1, 12:46 pm, sblantipodi wrote:
> I opened a similar thread recently but I doesn't let me enter any new
> post on it so I opened a new one.
>
> I'm having problem with LVL, I'm using
I'm getting the same problem. It works on two phones (Nexus One and
HTC Hero). Fails on a HTC Legend. Not sure whether that's important or
not!
I don't understand how it can say it's licensed.
On Aug 1, 11:46 am, sblantipodi wrote:
> I opened a similar thread recently but I doesn't let me enter
I'm seeing the same behavior using the sample activity, using the
gmail account that is associated with my developer account. The one
thing I haven't done is upload the sample activity APK to the Market.
Is that necessary?
On Aug 2, 12:45 pm, Trevor Johns wrote:
> It's a little hard to figure out
Trevor,
Can you clarify what the licensing server returns if the App is not in
the Android Market? In my experience (and it seems other people) it is
returning LICENSED. This does not seem sensible to me.
Thanks
Rob
On Aug 4, 3:23 am, Trevor Johns wrote:
--
You received this message because
Personal update. My problem was stupid beyond belief - Didn't see the
save button on the dev console and was expecting AJAX behavior from
the dropdown response selector. The sample app works as expected now.
On Aug 3, 11:00 am, OldSkoolMark wrote:
> I'm seeing the same behavior using the sample a
Necessary for final deployment. The sample program can be used for
testing by developers without uploading to the market.
On Aug 3, 7:23 pm, Trevor Johns wrote:
> Yes, it's necessary. We need the application to be listed in Android Market
> so that we can actually check and see if you've purchase
this answered all my questions,
"If an app is in draft (never published), then we send LICENSED for
all
requests for that app."
On Aug 7, 1:26 am, Trevor Johns wrote:
> If an app is not published AND not draft, then you'll get
> ERROR_NOT_MARKET_MANAGED.
>
> If an app is in draft (never publishe
I'm wondering if it would be better for all draft (never published)
apps to follow the rules set up in the Dev Console (rather than just
returning LICENSED)?
Because:
1. Its more intuitive to the dev (as can be seen from this thread)
2. It gives the dev more control - he can test an app fully (th
Mark you are obviously right, returning always licensed has no sense,
is no useful and doesn't give any help to developers.
I think that this behaviour is just lazyness from the google developer
side.
On Aug 8, 11:40 pm, Mark Carter wrote:
> I'm wondering if it would be better for all draft (neve
I do see this behaviour too (though dev account on emulator and test
account on N1). My next thing to try would be uploading my app (but
not publishing it) to see if that then gives back what I set in the
dev console... Though from previous answers I probably get back
LICENSED which as you say is n
I would love to see this information set out in tabular form. I'm
always suspicious of a missing case until I see a truth table of the
logic.
On Aug 6, 4:26 pm, Trevor Johns wrote:
> If an app is not published AND not draft, then you'll get
> ERROR_NOT_MARKET_MANAGED.
>
> If an app is in draft (n
Update: I uploaded and saved my exported signed app via the dev-
console but did not publish it.
With my test account on N1 I am now able to get returned from LVL what
I set in the dev console. So I'm not always getting LICENSED back, but
what I set the test response to, so it is configurable, so t
I have to say the google market is a really terrible implementation.
Ok fine I finally jumped through the hoops of LVL and I realized that
I need to have my latest app *uploaded* but not *published* in order
for the license check to work for my test accounts for the new
version.
BUT
Little did I
You can have the one your testing use the same "android:versionCode"
as one you already uploaded and it will allow you to test, without
having to upload a newer version.
This is what I did and it worked.
On Oct 24, 11:21 am, swinefeaster wrote:
> I have to say the google market is a really terri
is 'draft' the same as activated/not published (since last apk upload)?
If so, is there a delay between when it is counted as a draft and when it
is uploaded?
I have a draft (at least I believe I do), but I still get
ERROR_NOT_MARKET_MANAGED on a test-account
On Friday, August 6, 2010 4:26:28 PM
It's a little hard to figure out what the initial report is describing here,
but I suspect it's this:
The test response settings in the Market publisher console only affect users
who are (a) the developer who owns the publisher account, or (b) listed as
test accounts.
Normal users are unaffected
Yes, it's necessary. We need the application to be listed in Android Market
so that we can actually check and see if you've purchased it. (We send the
package name and version code of the application to the licensing server --
if your app isn't published, we won't find a match for the package name.
*I* only ever get LICENSED if I have set my Dev Console to return LICENSED.
If I set it to "Respond normally" I get NOT_MARKET_MANAGED.
Whatever I set it to in the dev console, other users will get
NOT_MARKET_MANAGED because the package name / version code combo is not
recognised by the Android Ma
If the app isn't in Android Market, the license server will return
ERROR_NOT_MARKET_MANAGED. LicenseValidator considers that to be a fatal
error due to programmer error, and should invoke the applicationError()
callback method.
My understanding from the server team is that uploading a draft versio
Yes, this is correct behavior. Just to confirm: This is for an application
that hasn't been published yet, correct?
(You shouldn't get NOT_MARKET_MANAGED, provided that the application has
been uploaded to the publisher console and, for existing apps, you've revved
the version code for your applic
So to confirm. If an app is not published (nor draft) then the response is
dictated by the user's (i.e. the user running the app, not the one who
developed the app) setting in the Dev Console. If the user does not have a
Dev account (like many beta testers) then the response will be like "Respond
n
If an app is not published AND not draft, then you'll get
ERROR_NOT_MARKET_MANAGED.
If an app is in draft (never published), then we send LICENSED for all
requests for that app.
If an app is published (or has been published then unpublished), then
the response
is driven by the dev console setting
Yes, the problem is for apps which have neither been published nor are in
draft.
In this scenario, it really does not make sense that the response is based
on the user's developer console settings. It would be much better if it
always returned ERROR_NOT_MARKET_MANAGED.
On 24 September 2010 13:17,
This is what I do too - not great, but I haven't found a better way yet.
On 25 October 2010 20:34, gcstang wrote:
> You can have the one your testing use the same "android:versionCode"
> as one you already uploaded and it will allow you to test, without
> having to upload a newer version.
>
> Th
26 matches
Mail list logo
