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 not very handy for real device testing...
On 27 aug, 11:21, Mark Carter <mjc1...@googlemail.com> wrote: > Can anyone else confirm this please? > > On Aug 20, 11:27 am, Mark Carter <mjc1...@googlemail.com> 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 account). The other (Hero > > running 2.1-update1) is a test account I use (no developer account). > > > When I use the N1, I always get the response specifed in my Dev > > Console settings. > > When I use the Hero, I always get ERROR_NOT_MARKET_MANAGED. > > > It appears the logic goes something like this for non-Market > > (published or draft) apps: > > > Check the user has a Dev account. > > If so, use the response set there. > > If not, return ERROR_NOT_MARKET_MANAGED. > > > Notice, its the setting for the user, not the dev (because theMarket > > does not know who the dev is), that is used. > > > Anyone confirm this? > > > On Aug 7, 1:26 am, Trevor Johns <tjo...@google.com> 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 published), then we sendLICENSEDfor 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 settings for the developer/testers, and > > > purely > > > by purchase history for everyone else. > > > > -- > > > Trevor Johns > > > Google Developer Programs, Androidhttp://developer.android.com > > > > On Thu, Aug 5, 2010 at 4:18 AM, Mark Carter <mjc1...@googlemail.com> > > > wrote: > > > > 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 > > > > normally"? > > > > > If the app is published (or draft) then the response is driven > > > > primarily by > > > > the dev's console settings and secondarily by theMarketlicense server > > > > (storing who has paid for what). > > > > > I think the first part could catch a lot of people out... > > > > > On 5 August 2010 11:03, Trevor Johns <tjo...@google.com> wrote: > > > > >> If the app isn't in AndroidMarket, 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 > > > >> version is > > > >> supposed to be sufficient to avoid getting ERROR_NOT_MARKET_MANAGED. > > > >> (In the > > > >> case of existing applications, you'll also need to increment your > > > >> version > > > >> code.) > > > > >> The other way you'll avoid this is precisely as Mark mentioned. If we > > > >> don't find the application, we check to see if the current user has a > > > >> developer account, and will send a test response (if one is set) using > > > >> the > > > >> user's RSA keypair. > > > > >> -- > > > >> Trevor Johns > > > > >> On Wed, Aug 4, 2010 at 12:30 AM, Kirky <rob.kirkbr...@gmail.com> wrote: > > > > >>> Trevor, > > > > >>> Can you clarify what the licensing server returns if the App is not in > > > >>> the AndroidMarket? In my experience (and it seems other people) it is > > > >>> returningLICENSED. This does not seem sensible to me. > > > > >>> Thanks > > > > >>> Rob > > > > >>> On Aug 4, 3:23 am, Trevor Johns <tjo...@google.com> wrote: > > > > >>> -- > > > >>> 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<android-developers%2Bunsubs > > > >>> cr...@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 post to this group, send email to > > > >> android-developers@googlegroups.com > > > >> To unsubscribe from this group, send email to > > > >> android-developers+unsubscr...@googlegroups.com<android-developers%2Bunsubs > > > >> cr...@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 post to this group, send email to android-developers@googlegroups.com > > > > To unsubscribe from this group, send email to > > > > android-developers+unsubscr...@googlegroups.com<android-developers%2Bunsubs > > > > cr...@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 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
