This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220: Android app SimpleLink Starter Pro will not build with the new version of Android Studio 3.0.1

Part Number: CC3220

I upgraded to the latest version of Android Studio 3.0.1

I downloaded the source code from TI, and then tried to build and got the following error:

Error:android-apt plugin is incompatible with the Android Gradle plugin.  Please use 'annotationProcessor' configuration instead.

I found this stackoverflow article which stated:

  The android-apt plugin has been deprecated.

  • Hi Nader,

    Thanks for bringing this to our attention. I'll have to check with our tools team about addressing this in our next release. I should have an answer by the end of the week.

    Thanks,
    Ben M
  • Hi nader,

    Even though this will not be addressed until another official release is made, our tools lead found a solution for compiling based on the new Android Studio + new gradle. Note this has not been formally tested, but it should get you going -

    Please try the following:

    1. File:  starter_pro_android\SmartConfigBitBite\app\build.gradle  new content (many changes)

    apply plugin: 'com.android.application'

    //apply plugin: 'android-apt'

    android {

    //    signingConfigs {

    //       config {

    //            storeFile file(System.getenv("RELEASE_STORE_FILE"))

    //            storePassword System.getenv("RELEASE_STORE_PASSWORD")

    //            keyAlias System.getenv("RELEASE_KEY_ALIAS")

    //            keyPassword System.getenv("RELEASE_KEY_PASSWORD")

    //        }

    //    }

       compileSdkVersion 21

       buildToolsVersion '26.0.2'

       defaultConfig {

           applicationId "com.ti.smartconfig"

           minSdkVersion 14

           targetSdkVersion 21

           javaCompileOptions {

               annotationProcessorOptions {

                   arguments = ['resourcePackageName': android.defaultConfig.applicationId]

               }

           }

       }

       buildTypes {

    //        release {

    //            minifyEnabled false

    //            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'

    //            signingConfig signingConfigs.config

    //            pseudoLocalesEnabled false

    //        }

       }

    }

    dependencies {

       compile 'com.android.support:support-v4:21.0.3'

       annotationProcessor "org.androidannotations:androidannotations:4.3.1"

       compile 'org.androidannotations:androidannotations-api:4.3.1'

       compile 'fr.avianey.com.viewpagerindicator:library:2.4.1@aar'

       compile files('libs/android-logging-log4j-1.0.3.jar')

       compile files('libs/jmdns-3.4.2-r353-1.jar')

       compile files('libs/jsoup-1.8.1.jar')

       compile files('libs/log4j-1.2.17.jar')

       compile files('libs/smartconfiglib2.jar')

    }

    2. File: starter_pro_android\SmartConfigBitBite\build.gradle

    Before:

      classpath 'com.neenbedankt.gradle.plugins:android-apt:1.4'

    After:

     //classpath 'com.neenbedankt.gradle.plugins:android-apt:1.4'

    3. File: starter_pro_android\SmartConfigBitBite\gradle.properties

    Add:

    android.enableAapt2=false

    Best Regards,

    Ben M

  • thanks, I gave it a try - however those changes seemed to have spawned errors in other areas, now I am getting the following error:

    C:\Users\nader\Desktop\android_textmewes-t1\android_textmewes-t1\app\build\intermediates\manifests\instant-run\debug\AndroidManifest.xml

    Error:(24) error: unknown element <action> found.

    Error:(24) unknown element <action> found.

    any solutions on this?

  • Hi Nader,

    You may want to run through the gradle plug-in migration here:

    https://developer.android.com/studio/build/gradle-plugin-3-0-0-migration.html

    Since this is not addressed in a formal release yet, you may have to take some additional steps to migrate. I recommend checking for a misplaced tag which could be causing an error as described in this discussion:

    https://stackoverflow.com/questions/46948498/android-studio-3-0-manifest-error-unknown-element-action-found

    Best Regards,

    Ben M