On Wed, Apr 29, 2009 at 1:54 PM, fdimeglio <[email protected]> wrote: > > Xavier, > > Yes I confirm that if you are using subversion and having a "libs" dir > in which you have: > > - your jar libraries > - the .svn dir > > then the build just crap out with ADT 0.9: the resulting .apk contains > everything except the signature and if you "zip -T project.apk" you > will see that the apk file is considered as non valid. > > This leads too to the EOCD error you see when trying to push the > broken apk file to an emulator or a device. > > When can we expect a fix for this issue ?
hopefully sometimes next week. We're adding a few more fixes. > btw I have seen other issues with ADT 0.9: the auto generated resource > file is not generated if you AndroidManifest file is containing <uses- > sdk minSdkVersion="2"> instead of <uses-sdk > android:minSdkVersion="2"> > This was working with SDK1.1 but with SDK1.5 you need to use the > "android:" prefix Yeah we've fixed that too. the minSdkVersion attribute must be in the android namespace (we've fixed the docs for it too) This has always been the case, it's just that ADT now parses this value to display a warning in case this conflicts with the build target. Unfortunately, if the <uses-sdk> node is present but the attribute isn't, there's a bug which prevent the rest of the build from happening. thanks Xav -- Xavier Ducrohet Android Developer Tools Engineer Google Inc. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
