Recently, I upgraded my android-SDK to Android M (API 22, MNC Preview). After this, every project reported errors when Eclipse was opened.
The error said: "Error executing aapt. please check aapt is present at ..\sdk\build-tools\23.0.0_rc1\aapt.exe".
After checking this *.exe file, I found that "aapt.exe" of 23.0.0_rc1 is at ..\23.0.0_rc1\bin\aapt.exe not like that of 22.0.1 at ..\22.0.1\aapt.exe. So, the location of aapt.exe is changed, but Eclipse can't realize that.
So, did Android do this on purpose or carelessly? How could I solve this problem in the case of no changing the original file structure?
I use Eclipse as well as Android Studio. So, I want to make sure Android SDK is OK for AS first, then it is Eclipse, So I don't change structure of SDK
Any tips will be appreciated. Thanks in advance.
P.S.:
- My OS is Windows 7 and Mac OS X;
- The version of ADT plugin for Eclipse is 23.0.6, which is up to date by now;
- Also, there is another error reported by a popup window when Eclipse starts: Error: Error parsing ...\sdk\system-images\android-22\android-wear\armeabi-v7a\devices.xml cvc-complex-type.2.4.d: found invalid contents started with an element of "d:skin". This child element shouldn't be here.