CODEWITHSUNDEEP
cordovavisual-studio-2013visual-studio-cordova
JLeiser
JLeiser

Reputation: 11

Multi-Device-Hybrid-Apps cannot build for android target import org.apache.cordova.*; error

---Update---

Did a repair on the vs2013mda_0.1.1.exe and updated in sdk manager This was suggested in a previous question and I updated before posting and just updated again.

SDK Tools 22.6.4 SDK Platform-Tools 19.0.2 SDK Build Tools 19.1

There most be something wrong with cordovalib not being found.

I can build in eclipse, but it will not run in emulator.

Just want to get this working in visual studio

---original post---

Evaluating Multi-Device-Hybrid-Apps - http://msdn.microsoft.com/en-us/vstudio/dn722381

clean win81 machine with vs2013 up2 and Multi-Device-Hybrid-Apps installed. Create new Multi-Device-Hybrid-Apps project and build succeeds for ripple.

Try to build for android emulator and receive 2 errors: Seems to be caused by import org.apache.cordova.*; failing.

Called microsoft and they never heard of this feature, they asked me to post on SO

Error   2   c:\bin\vs13\cordova\BlankCordovaApp1\BlankCordovaApp1\bld\Debug\platforms\android\cordova\build.bat: Command failed with exit code 2    c:\bin\vs13\cordova\BlankCordovaApp1\BlankCordovaApp1\EXEC  1   1   BlankCordovaApp1
Error   3   The command ""C:\Users\jayl\AppData\Roaming\npm\node_modules\vs-mda\vs-cli" build --platform "Android" --configuration "Debug" --projectDir . --projectName "BlankCordovaApp1" --buildServerUrl "" --buildTarget "AndroidEmulator"" exited with code 8. C:\Users\jayl\AppData\Roaming\npm\node_modules\vs-mda-targets\Microsoft.MDA.targets 68  5   BlankCordovaApp1

Upvotes: 1

Views: 1875

Answers (1)

Priyank
Priyank

Reputation: 1568

Update:

This appears to be a bug in the way the Android project is built when its base directory is "bin". The solution is to rename that directory to something else (e.g. "projects"). The build should then proceed without error.

This is a known issue due to an Android library being renamed recently. Open up the SDK manager and install the latest android build tools and this error should go away.

Upvotes: 2

Related Questions