[android-developers] Testing in-app purchases is incompatible with monotonically increasing Android versions

I'm debugging in-app purchases.  This requires me to create the app profile on the console and upload the apk (but not necessarily publish it).  With an invited test gmail account, I can then test in-app purchases.  The problem is, there is no way to upload changes to the app if I have to fix something.  Say I upload an apk with version number 1.  Google requires that I increase the apk number with every upload, so I have to increase the number to 2 to change the code, and version 3 to change it again.  I may go through numerous iterations of development getting the final code in place...but none of these are actual new releases, the app isn't even published yet!  I want the first published version to be version 1, regardless of any initial testing and there doesn't seem to be any way to do this.  If I delete the apk from the app description in the hopes of wiping out the version numbers so I can upload an apk with version 1, the ENTIRE app profile is destroyed and I have to create a new one from scratch, including the required screenshot uploads and other tedium unrelated to testing.  This imposes a tremendous burden on the debugging process.

Is there any way to do what I am trying to accomplish here?  I am at a loss.

Thank you.

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