且构网

分享程序员开发的那些事...
且构网 - 分享程序员编程开发的那些事

插件ID为'机器人'未找到(Android的工作室)

更新时间:2022-11-05 14:30:39

插件ID为'机器人'未找到(Android的工作室)

这个问题出现在我的Andr​​oid 0.6.1工作室打造金丝雀一个星期挣扎后我发现有啥不对的新工作室的版本。它不是关于摇篮,据我看到的。它发生在某些人,你知道为什么吗?因为有些人专门初级开发无意中在继续的方式,这种错误发生的只是创建新的项目后。问题是由活动的名字来让我解释给你一步一步

现在,当u创建新的项目,向导出现,这里是你的一步:

第一:
       您输入应用程序名称
第二:
       选择最低的SDK
第三:
       你的活动类型
向前 :
       您的活动名称

这里的点。如果您选择系统默认的我的活动

插件ID为'机器人'未找到(Android的工作室)

将出现错误,但如果你将其更改为自己的自定义名称,如myListactivity或任何其他自定义的。这个错误将不复存在。

I recently just switched to Android Studio 0.6.1 for app dev and I ran into an issue with gradle.

I get "Error:(1, 0) Plugin with id 'android' not found. I am quite new so any help would be appreciated.

Here is my build.gradle file:

apply plugin: 'android'

android {

    compileSdkVersion 19
    buildToolsVersion "19.1.0"

    defaultConfig {
        applicationId "com.b3dog.helloagain"
        minSdkVersion 15
        targetSdkVersion 19
        versionCode 1
        versionName "1.0"
    }

    buildTypes {
        release {
            runProguard false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
}

dependencies {

    compile fileTree(dir: 'libs', include: ['*.jar'])
}

this issue appears in my android studio 0.6.1 canary build so after a week struggling i found whats wrong with new studio version . its not about Gradle as far as i see . and it happen to some people and you know why ? because some people specially junior developer accidentally proceeding in way that this error occur just after create new project . problem came from name of your activity let me explain it to your step by step

now , when u create new project , wizard appear and here's your step :

first : you enter application name second : select your minimum sdk third : type of your activity forth : your activity name

here's the point . if you choose the system default"my activity

error will occur but if you change it to your own custom name such as "myListactivity" or any other custom One . this error will no longer exist .