Why start with the exception of my own application resources when it was not needed before?

Question

Recently, I was struck by a mysterious problem without explanation, which I somehow managed to solve .

The solution in itself creates a problem for me because I do not understand this: it forces me to direct Proguard to ignore all warnings regarding my own application package in its entirety .

-dontwarn com.bta.** 

Besides the problematic issue of ignoring warnings about the most error-prone codes in my development (most often changing code), I am puzzled by two questions:

• Why did this need suddenly appear? (I never had to do this before.)
• Why is this not required in other projects / applications that I am developing?

I believe that some new code or library that I introduced caused this (AdMob?), But what is the explanation for this? Why does a third-party library force me to turn off warnings about my own application resources?

What are the side effects of disabling alerts about my own application package completely (like me)?

Answer 1

Answering my own question:

After you spent too much time debugging those tools that were supposed to save me time, I discovered the source of the problem. This is a bug in the Android SDK tools . This is documented as was decided in r17, but I am using the last of today (June 18, 2012) and it has not been resolved! (see Comment 24). Comment 25 also describes a workaround that now allows me to continue my actual development.

Errors are a fact of life in complex systems. But the fact that neither Proguard nor the build tools that feed the Proguard input can provide any useful error message (in fact, they did exactly the opposite), suggests that something is violated in the "methodology" of the tools Android development recommended by Google .