That's cool but i never said "this doesn't work". In fact, for all we knew
it was working just fine until we went live and started messing with it and
saw that this was happening when the app was downloaded from the Play Store
and the Play Store was left running. Now my app has been pulled and we had
clients lined up ready to buy this engine. I posted the issue on several
Android Dev forums and got no response, that's why i filed the bug report.
Perhaps I still did jump the gun on that but at this point it seems only
someone from Google would or is even able to tell me that for sure, and its
not like there's a public hotline to the Play Store dev team.
But to state the issue again - this is a matter of the Play Store - a
separate application - taking focus away from our app and bringing itself
(the Play Store) back into view after an in-app purchase is made or any
purchase-related dialog box generated by the Play Store in interacted with.
This only happens if the Play Store is still running in the background - if
the app is downloaded and not used until later, when the Play Store is no
longer running, or if the Play Store app is manually stopped, in-app
purchases and other Play Store dialog interactions ("already purchased",
etc) happen as expected and the user is never taken from our app. So this
isn't exactly a clear-cut issue of whose end the error is on - I can
naturally assume the error is on my part all day but still the first
logical question i cant get past is how could i have any programatic
control over what the Play Store app does or does not do?
I don't know of any other specific app I can download and try to replicate
this same scenario - if you know of one (that i can test for free) Id be
grateful to know about it, just so I can see something that works.
I dont expect my problems to be solved for me - I've been working on the
Android platform for two years now - alone. This is the first time I have
been this stuck.
- Josh
On Wednesday, June 13, 2012 12:57:22 PM UTC-4, Kristopher Micinski wrote:
>
> Quite to the contrary, I don't see any short compilable code to
> reproduce your claim, just a snippet. You gave a good description,
> which is a start, but filing a bug report on something that seems to
> be working in hundreds of other apps seems misguided, and if you're
> going to blame the system, you need to have a lot of support behind
> you, past "this doesn't work."
>
> So, I'm saying, I'm sure it doesn't work for you, you've clarified
> that, but if you're blaming the *system* for doing something
> incorrectly, I highly doubt that, and you'll need to substantiate it..
>
> And I don't know that you can say I'm trolling you, you can check my
> name in this group's history to check that...
>
> kris
>
> On Wed, Jun 13, 2012 at 12:47 PM, kadmos <[email protected]> wrote:
> > i did. if all youre going to do is troll dude go somewhere else.
> >
> >
> >
> > On Wednesday, June 13, 2012 12:09:43 PM UTC-4, Kristopher Micinski
> wrote:
> >>
> >> Great, produce some code, then.
> >>
> >> On Wed, Jun 13, 2012 at 11:47 AM, kadmos <[email protected]> wrote:
> >> > Respectfully, I don't read "works well in other applications" as "yes
> >> > this
> >> > very same scenario has been tested with at least one other published
> >> > application and it is absolutely NOT suppose to happen." Our app
> "works
> >> > well" so long as Google Play has been closed after the app has been
> >> > downloaded and installed. If it hasn't, then we get this weird
> behavior
> >> > which was enough for my publisher to pull the app from the store. I
> have
> >> > no
> >> > problem gutting the project and starting from square one with this
> but i
> >> > would like to at least try and get a clue as to where i went wrong so
> I
> >> > don't repeat the mistake.
> >> >
> >> > Thanks
> >> >
> >> > - Josh
> >> >
> >> >
> >> >
> >> > On Wednesday, June 13, 2012 10:38:46 AM UTC-4, Kristopher Micinski
> >> > wrote:
> >> >>>
> >> >>> And can anyone verify that if Google Play is already running (i.e.
> if
> >> >>> the
> >> >>> itself app has just been purchased/downloaded, installed, and was
> >> >>> started
> >> >>> before the Google Play app was closed) that Google Play does NOT
> take
> >> >>> over
> >> >>> focus after an attempt at an in-app purchase?
> >> >>>
> >> >>
> >> >> It looks like Dianne did:
> >> >> "Obvious this is not normal, since it works well in other
> >> >> applications. "
> >> >>
> >> >>
> >> >> kris
> >> >>
> >> > --
> >> > 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 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 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
