Basically if the Play Store app is still running in the background - which is going to be the case for most users once they first download and install the app - after interaction with any in-app purchase-related dialog box the Play Store is brought back into focus and users must make there way back to the app to complete tasks. how can this be prevented?
Obvious this is not normal, since it works well in other applications. You
have not supplied *any* information about what you are doing that may be of
interest, so nobody can do anything but make wild guesses about what you
are doing. So here are some wild guesses:
- Don't launch it with FLAG_ACTIVITY_NEW_TASK.
- Don't use android:launchMode="singleInstance" in your manifest.
On Tue, Jun 12, 2012 at 7:36 AM, kadmos <kadmo...@gmail.com> wrote:
> Anyone know what could be done about this?
> Basically if the Play Store app is still running in the background - which
> is going to be the case for most users once they first download and install
> the app - after interaction with any in-app purchase-related dialog box the
> Play Store is brought back into focus and users must make there way back to
> the app to complete tasks. how can this be prevented?
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
Note: please don't send private questions to me, as I don't have time to
provide private support, and so won't reply to such e-mails. All such
questions should be posted on public forums, where I and others can see and
answer them.
Thanks for the response. I have verified that * android:launchMode="singleInstance"* is nowhere in my manifest and * FLAG_ACTIVITY_NEW_TASK.*
Basically, our app has a Store activity, which acts as the point of sale. The *onCreate()* method of this activity starts the BillingService like so: startService(new Intent(myContext, BillingService.class));
The BillingService *onServiceConnected()* method instantiates * IMarketBillingService*:
The BillingHelper.class defines the *requestPurchase()* method called by the Store activity upon a button click: protected static void requestPurchase(Context activityContext, String itemId){
I have been told that a similar app to ours does not launch Google Play as a separate process, though ours does. Seems relevant but I have not enough knowledge to determine how.
On Tuesday, June 12, 2012 12:15:35 PM UTC-4, Dianne Hackborn wrote:
> Obvious this is not normal, since it works well in other applications. > You have not supplied *any* information about what you are doing that may > be of interest, so nobody can do anything but make wild guesses about what > you are doing. So here are some wild guesses:
> - Don't launch it with FLAG_ACTIVITY_NEW_TASK. > - Don't use android:launchMode="singleInstance" in your manifest.
> On Tue, Jun 12, 2012 at 7:36 AM, kadmos <kadmo...@gmail.com> wrote:
>> Anyone know what could be done about this?
>> Basically if the Play Store app is still running in the background - >> which is going to be the case for most users once they first download and >> install the app - after interaction with any in-app purchase-related dialog >> box the Play Store is brought back into focus and users must make there way >> back to the app to complete tasks. how can this be prevented?
>> -- >> 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+unsubscribe@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en
> Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them.
My apologies - seems some text got clipped - i meant to write "...and * FLAG_ACTIVITY_NEW_TASK* is nowhere in any of my code or in any of the code I borrowed from the tutorials."
On Tuesday, June 12, 2012 3:17:35 PM UTC-4, kadmos wrote:
> Hi Dianne,
> Thanks for the response. I have verified that * > android:launchMode="singleInstance"* is nowhere in my manifest and * > FLAG_ACTIVITY_NEW_TASK.*
> Basically, our app has a Store activity, which acts as the point of sale. > The *onCreate()* method of this activity starts the BillingService like > so: > startService(new Intent(myContext, BillingService.class));
> The BillingService *onServiceConnected()* method instantiates * > IMarketBillingService*:
> The BillingHelper.class defines the *requestPurchase()* method called by > the Store activity upon a button click: > protected static void requestPurchase(Context activityContext, > String itemId){
> I have been told that a similar app to ours does not launch Google Play as > a separate process, though ours does. Seems relevant but I have not enough > knowledge to determine how.
> - Josh
> On Tuesday, June 12, 2012 12:15:35 PM UTC-4, Dianne Hackborn wrote:
>> Obvious this is not normal, since it works well in other applications. >> You have not supplied *any* information about what you are doing that may >> be of interest, so nobody can do anything but make wild guesses about what >> you are doing. So here are some wild guesses:
>> - Don't launch it with FLAG_ACTIVITY_NEW_TASK. >> - Don't use android:launchMode="singleInstance" in your manifest.
>> On Tue, Jun 12, 2012 at 7:36 AM, kadmos <kadmo...@gmail.com> wrote:
>>> Anyone know what could be done about this?
>>> Basically if the Play Store app is still running in the background - >>> which is going to be the case for most users once they first download and >>> install the app - after interaction with any in-app purchase-related dialog >>> box the Play Store is brought back into focus and users must make there way >>> back to the app to complete tasks. how can this be prevented?
>>> -- >>> 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+unsubscribe@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/android-developers?hl=en
>> Note: please don't send private questions to me, as I don't have time to >> provide private support, and so won't reply to such e-mails. All such >> questions should be posted on public forums, where I and others can see and >> answer them.
Can some one at least verify for me that Google Play being launched as a separate process is NOT the correct behavior of an in-app billing activity?
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?
On Tuesday, June 12, 2012 12:15:35 PM UTC-4, Dianne Hackborn wrote:
> Obvious this is not normal, since it works well in other applications. > You have not supplied *any* information about what you are doing that may > be of interest, so nobody can do anything but make wild guesses about what > you are doing. So here are some wild guesses:
> - Don't launch it with FLAG_ACTIVITY_NEW_TASK. > - Don't use android:launchMode="singleInstance" in your manifest.
> On Tue, Jun 12, 2012 at 7:36 AM, kadmos <kadmo...@gmail.com> wrote:
>> Anyone know what could be done about this?
>> Basically if the Play Store app is still running in the background - >> which is going to be the case for most users once they first download and >> install the app - after interaction with any in-app purchase-related dialog >> box the Play Store is brought back into focus and users must make there way >> back to the app to complete tasks. how can this be prevented?
>> -- >> 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+unsubscribe@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en
> Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them.
> 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. "
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.
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. "
On Wed, Jun 13, 2012 at 11:47 AM, kadmos <kadmo...@gmail.com> 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 android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
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 <kadmo...@gmail.com> 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 android-developers@googlegroups.com > > To unsubscribe from this group, send email to > > android-developers+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en
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...
On Wed, Jun 13, 2012 at 12:47 PM, kadmos <kadmo...@gmail.com> 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 <kadmo...@gmail.com> 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 android-developers@googlegroups.com
>> > To unsubscribe from this group, send email to
>> > android-developers+unsubscribe@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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
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.
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 <kadmo...@gmail.com> 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 <kadmo...@gmail.com> 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 > android-developers@googlegroups.com > >> > To unsubscribe from this group, send email to > >> > android-developers+unsubscribe@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+unsubscribe@googlegroups.com > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en
On Wed, Jun 13, 2012 at 12:47:50PM -0700, kadmos wrote:
> 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.
I believe the point was, if you don't post the relevant portion of your
code, how does ANYONE know that it's not YOUR code that's wrong? Nobody
here (that I know of) is a mind reader. You're saying that Google's code
is wrong, while it's working everywhere else except your app, and you
won't post the relevant code from your app. How is anyone to asume
anything other than that the flaw is in your app? Think about it....
Then post the relevant portion of your code, and maybe, if you haven't
already been added to everyone's "send straight to /dev/null" list, you
might actually get some help fixing your app.
Later,
--jim
-- THE SCORE: ME: 2 CANCER: 0
73 DE N5IAL (/4) | "This 'telephone' has too many
spooky1...@gmail.com | shortcomings to be seriously considered
< Running Mac OS X Lion > | as a means of communication. The device
ICBM / Hurricane: | is inherently of no value to us."
30.44406N 86.59909W | (Western Union internal memo, 1876)
Can someone answer the below question? I have been testing this app, and when the app is launched, and the BUY button is pressed for an in-app purchase, It launches google play as a separate process. While testing a similar app "COMIXOLOGY" when making an in-app purchase, it *does not*launch google play as a process. In comixology it just shows the google play purchase page and goes away / returns to the app once you make the purchase.
On Wednesday, June 13, 2012 10:30:31 AM UTC-4, kadmos wrote:
Can some one at least verify for me that Google Play being launched as a separate process is NOT the correct behavior of an in-app billing activity?
I never said Google's code was wrong. I never said my code was *not* wrong. I *did* post relevant portions of my code - everything up to the actual point of initiating a purchase. if no one here can even follow that and relate it to the behavior described, or ask me for something specific, why should i bother posting even *more* code?
Tell you what everyone if you dont have any actual experience implementing in-app billing then please *do* add me to your *"send straight to /dev/null" * list so at least my thread won't get cluttered up with more condescending comments by folks offering nothing but attempts at putting words in my mouth.
On Wednesday, June 13, 2012 5:53:05 PM UTC-4, Spooky wrote:
> On Wed, Jun 13, 2012 at 12:47:50PM -0700, kadmos wrote:
> > 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.
> I believe the point was, if you don't post the relevant portion of your > code, how does ANYONE know that it's not YOUR code that's wrong? Nobody > here (that I know of) is a mind reader. You're saying that Google's code > is wrong, while it's working everywhere else except your app, and you > won't post the relevant code from your app. How is anyone to asume > anything other than that the flaw is in your app? Think about it.... > Then post the relevant portion of your code, and maybe, if you haven't > already been added to everyone's "send straight to /dev/null" list, you > might actually get some help fixing your app.
> Later, > --jim
> -- > THE SCORE: ME: 2 CANCER: 0 > 73 DE N5IAL (/4) | "This 'telephone' has too many > spooky1...@gmail.com | shortcomings to be seriously considered > < Running Mac OS X Lion > | as a means of communication. The device > ICBM / Hurricane: | is inherently of no value to us." > 30.44406N 86.59909W | (Western Union internal memo, 1876)
On Wed, Jun 13, 2012 at 7:13 PM, kadmos <kadmo...@gmail.com> wrote:
> I never said Google's code was wrong. I never said my code was not wrong. I
> did post relevant portions of my code - everything up to the actual point of
> initiating a purchase. if no one here can even follow that and relate it to
> the behavior described, or ask me for something specific, why should i
> bother posting even more code?
> Tell you what everyone if you dont have any actual experience implementing
> in-app billing then please do add me to your "send straight to
> /dev/null" list so at least my thread won't get cluttered up with more
> condescending comments by folks offering nothing but attempts at putting
> words in my mouth.
> Thanks
I do have experience implementing this, but you never posted an app
that actually compiled, in general people aren't going to go to the
work of creating a new project, and writing code around the snippet
your provided.
I also didn't make any condescending comments, you filed a bug report,
the title of the report was "Play Store hijacking focus after in-app
purchase dialog." I'm sorry, I just didn't understand that that
statement wasn't meant to imply the system was wrong. To me, you
should only be filing a bug report on a system app if you believe that
it is written in. I apologize for the "produce some code" comment,
but the example you gave would require people to spend a few hours
pulling that into an open project, stepping through it, and
reproducing your error; I was simply saying that you'd perhaps get
more help if you gave a more approachable example. I apologize for
giving you the impression that I didn't care about your situation, but
you are also acting aggressive. With the amount of information you've
given up to this point, Dianne's advice is the only thing that comes
to mind,
On Wed, Jun 13, 2012 at 7:13 PM, kadmos <kadmo...@gmail.com> wrote:
> I never said Google's code was wrong. I never said my code was not wrong. I
> did post relevant portions of my code - everything up to the actual point of
> initiating a purchase. if no one here can even follow that and relate it to
> the behavior described, or ask me for something specific, why should i
> bother posting even more code?
1. When you tested your app on a handful of different devices, did the
behavior you dislike persist across all of them?
2. When you tested a bunch of other apps' in-app purchases on a device
that is giving you grief, did they exhibit the same behavior?
3. Does the sample app have enough commonality in logic that you can
determine if it exhibits the same behavior?
> Can some one at least verify for me that Google Play being launched as a separate process is NOT the correct behavior of an in-app billing activity?
Google Play, by definition, will ALWAYS be in a separate process. The
only stuff in your process is code in your app (code you wrote, code
you added via a JAR or library project, code in framework classes).
In-app purchasing code might be in your app (depending on what you
copied from samples, etc.); Google Play itself is not.
> I don't know of any other specific app I can download and try to replicate this same scenario
By your own admission, "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". Hence, the problem should be visible in any app
implementing in-app purchases where the Play Store in the state you
described ("which is going to be the case for most users once they
first download and install the app"). Finding apps that implement
in-app purchases is not especially difficult, even if you can't
directly search for that.
> 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."
By your own admission, this will happen for every single in-app
purchase where the Play Store in the state you described ("which is
going to be the case for most users once they first download and
install the app"). You should be capable, therefore, to test this with
at least one other published application, and preferably more than
one.
> *"...you filed a bug report, the title of the report was "Play Store > hijacking focus after in-app purchase dialog." I'm sorry, I just didn't > understand that that statement wasn't meant to imply the system was wrong." > *
I believed it was a concise and accurate enough observation of what was happening, which was all i had (and still have) to go on. Hoped it would be enough to catch the attention of someone who may have experienced the same problem.
*"To me, you should only be filing a bug report on a system app if you believe that it is written in."* * * I will be mindful of this from now on. Actually had I been a member of this group at the time and able to post (i thought i had joined a while back but apparently not) i probably would have just started this thread and not bothered with the bug report.
* "I apologize for the "produce some code" comment, but the example you gave would require people to spend a few hours pulling that into an open project, stepping through it, and reproducing your error"* * * I wasn't expecting anyone to do all that. I was hoping this was either a common, easily-resolvable issue, or in fact a legitimate bug with the Play Store, and that someone could call it either way. As i said before i have no issue with sucking it up and starting over, its just frustrating to have been this close just to have it fall apart now.
On Wed, Jun 13, 2012 at 04:13:41PM -0700, kadmos wrote:
> I never said Google's code was wrong. I never said my code was *not* wrong.
1) Look at your subject line, if nothing else: "Play Store hijacking" ... That is not exactly implying good behavior on the part of the market.
2) You filed a bug report about the Play Store, did you not? That's what
I read here. Doing so implies that you believe the problem is there,
and not your app.
3) I was in no way trying to be condescending. If you mis-read my post
that way, well, you read it wrong.
> I *did* post relevant portions of my code - everything up to the actual > point of initiating a purchase.
I thought the problem was either during or after the in-app purchase....
If it's before the in-app purchase, then why does your subject line
specify AFTER in-app purchase? Code prior to that is not the relevant
code people are asking for. Sorry if you disagree, but that's just how
it is here. People are not going to try to reconstruct what you did,
by guessing and/or trying to read your mind.... Post the suspected
problem code, along with all errors associated with it.
> if no one here can even follow that and relate it to the behavior
> described, or ask me for something specific, why should i bother
> posting even *more* code?
Perhaps because people here are asking you to post the code that's
actually relevant to the issue you are describing, so they can try
to help you? OR, perhaps nobody has ever SEEN this error except you.
If you don't want to post the code, fine...but don't be surprised
if you don't get as much/any help, or if you don't get the right help.
Again, NOT being condescending, just honest.
Later,
--jim
-- THE SCORE: ME: 2 CANCER: 0
73 DE N5IAL (/4) | Peter da Silva: No, try "rm -rf /"
spooky1...@gmail.com | Dave Aronson: As your life flashes before
< Running Mac OS X Lion > | your eyes, in the unit of time known as an
ICBM / Hurricane: | ohnosecond.... (alt.sysadmin.recovery)
30.44406N 86. 59909W |
1. When you tested your app on a handful of different devices, did the
> behavior you dislike persist across all of them?
yes. 3 different ones.
> 2. When you tested a bunch of other apps' in-app purchases on a device > that is giving you grief, did they exhibit the same behavior?
i myself have not tested any other apps' in-app purchases because i don't know of any to test. Another app (comiXology) was tested (not by me personally) and has been used as comparison this entire time - not only was the same behavior not reported, but it was noticed that when initiating a purchase with comiXology, the Play Store is not launched or seen as a separate running process, where as it was with ours. It was speculated that this may have something to do with the Play Store taking focus from our app but i don't know where to go with it - don't know how to initiate in-app billing any other way than with the code that's available in the tutorials.
> 3. Does the sample app have enough commonality in logic that you can > determine if it exhibits the same behavior?
I suppose so. We obviously did not publish it and download it form the Play Store to do a truly accurate comparison but i did not think to compile it onto my device and run it with the Play Store still running. I just tried and it worked as it should i suppose - i was returned to the app after "completing" a purchase. Going from this point, our app, assuming the correct response code is received, begins an asynchronous file download. It's at this point we find our app will be pushed to the background and the Play Store brings itself back into view in whatever state it was left - usually the download page for our app.
> * > "Google Play, by definition, will ALWAYS be in a separate process. The > only stuff in your process is code in your app (code you wrote, code > you added via a JAR or library project, code in framework classes). > In-app purchasing code might be in your app (depending on what you > copied from samples, etc.); Google Play itself is not. "*
I would have assumed this - i was only told otherwise by someone making purchases with comiXology who was observing the processes running on their device, comparing that app to ours.
*"I thought the problem was either during or after the in-app purchase....
>> If it's before the in-app purchase, then why does your subject line >> specify AFTER in-app purchase? Code prior to that is not the relevant >> code people are asking for*."
Because the only relevant(?) feedback i've gotten from anyone was that another app was not launching the Play Store as a separate process at the point of sale, whereas ours was, so the first thing i wanted to do was rule out that i was beginning the process incorrectly and, by that, somehow allowing the Play Store to take focus after an in-app purchase screen. To be clear, our app still "works" after a purchase, its just that the Play Store has to be backed out of or closed, and then you can see our app, downloading new content, the record of the purchase is in the account, etc. everything else is as it should be.
* "People are not going to try to reconstruct what you did" *
I wasnt expecting or asking anyone to do this. I was hoping someone would have already had this problem or someone would at least be able to identify the symptom by what i described.
Google Play will always be launched as a separate *process*, as Mark
already pointed out above.
It may or may not be on the requesting app's activity stack, depending on
the Android version (1.6 or above - although I suspect one would have to
search high and low for a 1.6 device at this time).
Here is a logcat snippet from my own app's purchase process:
Search for "Using the pending intent", it's at the very end of the section.
There is a short note after the code snippet that's also worth checking out:
Important: You must launch the pending intent from an activity context and
not an application context. Also, you cannot use the singleTop launch mode
to launch the pending intent. If you do either of these, the Android system
will not attach the pending intent to your application process. Instead, it
will bring Google Play to the foreground, disrupting your application.
> Can someone answer the below question? I have been testing this app, and
> when the app is launched, and the BUY button is pressed for an in-app
> purchase, It launches google play as a separate process. While testing a
> similar app "COMIXOLOGY" when making an in-app purchase, it *does not*launch google play as a process. In comixology it just shows the google
> play purchase page and goes away / returns to the app once you make the
> purchase.
> On Wednesday, June 13, 2012 10:30:31 AM UTC-4, kadmos wrote:
> Can some one at least verify for me that Google Play being launched as a
> separate process is NOT the correct behavior of an in-app billing activity?
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
When you get this behavior to occur, try taking snapshots of the activity stack via adb shell dumpsys activity
Do this at each step of the in-app purchase flow for your app to see what exactly is and is not a part of your apps history stack. You may have mis-configured activity and task launching which is causing this problem.
On Tuesday, June 12, 2012 10:36:30 AM UTC-4, kadmos wrote:
> Anyone know what could be done about this?
> Basically if the Play Store app is still running in the background - which > is going to be the case for most users once they first download and install > the app - after interaction with any in-app purchase-related dialog box the > Play Store is brought back into focus and users must make there way back to > the app to complete tasks. how can this be prevented?
> 1. When you tested your app on a handful of different devices, did the
>> behavior you dislike persist across all of them?
> yes. 3 different ones.
>> 2. When you tested a bunch of other apps' in-app purchases on a device >> that is giving you grief, did they exhibit the same behavior?
> i myself have not tested any other apps' in-app purchases because i don't > know of any to test. Another app (comiXology) was tested (not by me > personally) and has been used as comparison this entire time - not only was > the same behavior not reported, but it was noticed that when initiating a > purchase with comiXology, the Play Store is not launched or seen as a > separate running process, where as it was with ours. It was speculated that > this may have something to do with the Play Store taking focus from our app > but i don't know where to go with it - don't know how to initiate in-app > billing any other way than with the code that's available in the tutorials.
>> 3. Does the sample app have enough commonality in logic that you can >> determine if it exhibits the same behavior?
> I suppose so. We obviously did not publish it and download it form the > Play Store to do a truly accurate comparison but i did not think to compile > it onto my device and run it with the Play Store still running. I just > tried and it worked as it should i suppose - i was returned to the app > after "completing" a purchase. Going from this point, our app, assuming the > correct response code is received, begins an asynchronous file download. > It's at this point we find our app will be pushed to the background and the > Play Store brings itself back into view in whatever state it was left - > usually the download page for our app.
>> * >> "Google Play, by definition, will ALWAYS be in a separate process. The >> only stuff in your process is code in your app (code you wrote, code >> you added via a JAR or library project, code in framework classes). >> In-app purchasing code might be in your app (depending on what you >> copied from samples, etc.); Google Play itself is not. "*
> I would have assumed this - i was only told otherwise by someone making > purchases with comiXology who was observing the processes running on their > device, comparing that app to ours.
Did you find some resolution to this, if you are still having an
issue, it seems like you've invested some time in this, and if you
really think it's an Android bug, and you have a reproducible test
case in the form of a project (though in app purchasing stuff is just
a pain to debug for obvious reasons) people could try taking a look.?
On Mon, Jun 18, 2012 at 1:13 AM, kadmos <kadmo...@gmail.com> wrote:
>> thank you everyone for your time and assistance
> - j
> --
> 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+unsubscribe@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en
