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 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. > >> >> >> >>
-- 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
