On Wed, Jun 13, 2012 at 7:13 PM, kadmos <[email protected]> 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.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
_The Busy Coder's Guide to Android Development_ Version 3.7 Available!
--
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
