Why Can't Google's Market Billing Sample Build in a Signed Release Version?

Question

I tried looking into similar problems, but the solutions offered there do not seem to fit my particular situation:

I initially followed the instructions for Configur

Answer 1

Short answer: Because Eclipse + ADT sucks. That's why.

Longer answer: I just imported the same exact project to a different machine with a slightly different configuration: Eclipse 3.6.2 (instead of 3.6.1 in the problematic system described above) and SDK R13 (instead of R9 in the problematic system).

Then I tried to export it, using the same exact steps described above. Works like a charm!

What is this? Voodoo?

What happened to the days in which the IDE behaved more predictably than the software I was trying to develop?

Next step: Upgrade Eclipse (to 3.6.2) only, on the problematic system and see whether this solves the problem in that system, too.

Update: I just finished updating Eclipse 3.6.1 to 3.6.2 on the offending system. It turns out that it is impossible to install Eclipse and keep the existing ADT. https://dl-ssl.google.com/android/eclipse/ forces you to install "the latest & greatest" even if you want otherwise (for configuration management & tracking reasons for example). So with the new Eclipse 3.6.2 I got ADT 16.0.0.v201112150204-238534 as well. Works like a charm!

The root cause and explanation for the odd behavior of the combination Eclipse 3.6.1 + ADT 9.0.1.v201101191456-93220 will never be known... and this is a combo with which developers were supposed to (and did) release commercial grade apps to the Android Market at some point in time. Amazing.

Answer 2

I too had the same issue and i solved it by :

1. Delete bin & gen folder
2. Remove the dependency libraries(if any) and add them back
3. Finally clean up the project and build it again.

Done!