Bug 12633 - platform-tools for Android SDK have moved, preventing Studio builds
Summary: platform-tools for Android SDK have moved, preventing Studio builds
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Tools and Addins ()
Version: 4.7.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-06-11 12:58 UTC by Andrew Fernandes
Modified: 2013-06-11 17:52 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Andrew Fernandes 2013-06-11 12:58:57 UTC
In a recent Android SDK version update (Android SDK Tools: 22.0.1, Android SDK Platform-tools: 17, Android SDK Build-tools: 17), the location of the build tools have moved.

Since Xamarin Studio (4.0.8) uses hardcoded paths, the build command '${SDK_DIR}/platform-tools/aapt' fails since the 'aapt' file does not exist at that location. That file, *along with others*, have moved to '${SDK_DIR}/build-tools/17.0.0/aapt'.

For now, symbolic links in the platform-tools directory solve the issue. But that's hackish and interferes with non-Xamarin build systems.
Comment 1 Jonathan Pryor 2013-06-11 16:49:03 UTC
Which version of Xamarin.Android are you using? This should have been fixed in 4.6.6 (stable) and 4.7.5 (alpha) (though you'll need 4.7.6 on Windows).

http://docs.xamarin.com/releases/android/xamarin.android_4/xamarin.android_4.6.6
http://docs.xamarin.com/releases/android/xamarin.android_4/xamarin.android_4.7#Xamarin.Android_4.7.5
Comment 2 Andrew Fernandes 2013-06-11 17:52:24 UTC
Too funny; I'm the missing sandwich-filling... I'm on 4.7.4 in the beta channel. Alpha is a little too bleeding-edge for me! :-)

So stable - fixed, alpha- fixed, beta - not fixed. :-) Not that big of a deal...