Compiling problems after updating please help

ionic-v1
1

Console
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[
sh-3.2# ionic build android
Running command: /Applications/MAMP/htdocs/miguarimba/hooks/after_prepare/010_add_platform_class.js /Applications/MAMP/htdocs/miguarimba
add to body class: platform-android
Running command: /Applications/MAMP/htdocs/miguarimba/platforms/android/cordova/build
ANDROID_HOME=/Applications/ADT/sdk
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/Home
Running: /Applications/MAMP/htdocs/miguarimba/platforms/android/gradlew cdvBuildDebug -b /Applications/MAMP/htdocs/miguarimba/platforms/android/build.gradle -Dorg.gradle.daemon=true

FAILURE: Build failed with an exception.

  • What went wrong:
    A problem occurred configuring root project ‘android’.

Could not resolve all dependencies for configuration ‘:_debugCompile’.
Could not find any version that matches com.android.support:support-v4:+.
Searched in the following locations:
https://repo1.maven.org/maven2/com/android/support/support-v4/maven-metadata.xml
https://repo1.maven.org/maven2/com/android/support/support-v4/
Required by:
:android:unspecified
Could not find any version that matches com.android.support:support-v13:23+.
Searched in the following locations:
https://repo1.maven.org/maven2/com/android/support/support-v13/maven-metadata.xml
https://repo1.maven.org/maven2/com/android/support/support-v13/
Required by:
:android:unspecified
Could not find any version that matches com.google.android.gms:play-services-gcm:+.
Searched in the following locations:
https://repo1.maven.org/maven2/com/google/android/gms/play-services-gcm/maven-metadata.xml
https://repo1.maven.org/maven2/com/google/android/gms/play-services-gcm/
Required by:
:android:unspecified

  • Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
    [[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[
    HELP me…
2

Perhaps you’ve figured it out already, but as per some other posts I discovered that I had to update my Android SDK extras. If you run the SDK manager and install all the extras that seemed to work for me. I had to scroll all the way to the bottom of the SDK manager window to find them which is why I missed them the first time.

1 Like