locked
aapt.exe bug RRS feed

  • Question

  • User28819 posted

    On 4.12.1 i often see following problem on my build machine. 4.10 was okay.

    [Aapt] C:\Program Files (x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(752, 2): error MSB6003: The specified task executable "aapt.exe" could not be run. The filename or extension is too long

    Is there any workaround for that ?

    Tuesday, March 18, 2014 9:46 PM

All replies

  • User35 posted

    I guess it depends on where your Android SDK is located. If it's buried very deeply in a folder structure, the path could be to long for Windows. You could try using an Android SDK situated in another location (i.e. C:\android-sdk).

    Wednesday, March 19, 2014 1:49 PM
  • User28819 posted

    The path is longer than 32000 symbols. Seems like a bug in xamarin infrastructure that concatenates strings for cmd commands.

    Monday, March 24, 2014 12:50 PM
  • User27717 posted

    Can confirm unrelated to SDK path, my path is short and this happened today. Cleaning and rebuilding is a valid workaround

    Friday, April 4, 2014 5:09 PM
  • User27717 posted

    Had another look at this now its cropped up again in my build. Basically aapt is being called with over 100 "-j obj\Debug\libraryprojects\numberfile.jar" for each file.jar with different numbers each time, end result is an utter mess! Given this is resolved by cleaning, it would seem something is not keeping track of the library_projects folder

    Monday, April 7, 2014 10:12 AM
  • User12447 posted

    for reference, I have filed a bug report regarding this issue (including a VS solution for demonstration) on https://bugzilla.xamarin.com/show_bug.cgi?id=20744. Hope this can be fixed.

    Friday, June 20, 2014 3:57 AM