Conclusion: if you face this, blame proguard that comes with r12 tools
(v4.4). Simplest solution is to grab v4.6 from proguard website and just
replace files in SDK\tools\proguard\lib from these found in 4.6 archive.
Regards,
Marcin Orlowski
*Tray Agenda http://bit.ly/trayagenda* - keep you
I ran into the same issue last night.
This worked:
http://stackoverflow.com/questions/6605971/android-sdk-tools-revision-12-has-problem-with-proguard-error-conversion-to-d
Same workaround is also reported here:
http://code.google.com/p/android/issues/detail?id=18359
-- Kostya
31.07.2011
On Jul 31, 2011 4:04 PM, Kostya Vasilyev kmans...@gmail.com wrote:
http://code.google.com/p/android/issues/detail?id=18359
you mean .bat change? did not worked for me (plus afaik it's wrong
approach). still it's worth updating proguard anyway - 4.4 is dated
february, and 4.6 is lastest
--
You
Yep, a .bat file change fixed it for me (I also banged my head against
the desk for a while, too - not sure if that had any effect).
I actually used to use ProGuard 4.6, installed separately, but ADT 12
seems to always use its own version 4.4 (ignoring proguard.dir in
local.properties).
So,
On 30 July 2011 15:28, Marcin Orlowski webnet.andr...@gmail.com wrote:
Hi,
Is there any easy way (with Eclipse) to find out what exactly caused this
error? Project was building for ages just fine, and now it causes this error
when I try to export signed apk. I am wondering what code exactly
5 matches
Mail list logo
