Try disassembling comiXology and see how it works there.
Am Donnerstag, 14. Juni 2012 03:12:07 UTC+2 schrieb kadmos:
>
>
> 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
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).
He
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
*"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'
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
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
>
> *"...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 w
On Wed, Jun 13, 2012 at 7:13 PM, kadmos 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 d
On Wed, Jun 13, 2012 at 7:13 PM, kadmos 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 d
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
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
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 w
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
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 wrote:
> > Respectfully, I don't read "works well in other applications"
Great, produce some code, then.
On Wed, Jun 13, 2012 at 11:47 AM, kadmos 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 "w
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 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 Di
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
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."
- Josh
On Tuesday, June 12, 2012 3:17:35 PM UTC-4, kadmos wrote:
>
> Hi Dianne,
>
> Thanks for the response. I have
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 li
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_AC
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 ba
22 matches
Mail list logo
