OK, I solved it - it really was a @googlemail.com / @gmail.com problem. I entered the corresponding @gmail.com address as test account, and In- app billing started to work. It seems to be an issue at Google, so I entered a new issue here: http://code.google.com/p/marketbilling/issues/detail?id=4 I hope they will catch up and solve this problem before In-app billing goes live - although it should only affect some users (e.g. Germany). IMHO they really should stop to allow these @googlemail.com accounts.
Regards Marc Reichelt || http://www.marcreichelt.de/ On 26 Mrz., 14:18, Kostya Vasilyev <[email protected]> wrote: > 26.03.2011 15:57, Marc Reichelt пишет: > > > Hi Kostya, > > > of course they did charge your account for real > > Why the "of course"? I set this phone up as a test account in the Market > console, and "the system" knows this. > > > - you_definitely_ > > should read the In-app documentation before doing anything > > Yes, definitely plan to, when I actually start implementing it in my > app. So far I've only had time for a first, cursory read. > > Anyway, it was only $0.99, less than half the price of a pack of > cigarettes. And I can issue a refund to myself. > > > And as I pointed out I am using a correctly signed release build, not > > the debug build. Still having problems. > > Weird. From your description, we have identical setups: release builds > uploaded but not published, installed on the phone, item published in > the console, Market 2.3.4. And yet it worked for me and didn't work for you. > > -- Kostya > > > Regards > > > Marc Reichelt ||http://www.marcreichelt.de/ > > -- > Kostya Vasilyev --http://kmansoft.wordpress.com -- 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
