Android Studio Marks syntax as error, but gradle compiles

I don't know how to add a library using MavenCentral. I follow these steps to include a library

1. Add library in App_Name/App_Name/libs folder.
2. In App_Name/build.gradle add this

dependencies {

compile ---

compile files('libs/fileName.jar') }

3. ./gradlew clean
4. Make sure your Android studio is updated.

These are not errors actually, this a bug in Android studio( 0.4.2 ) for resolving the symbol and fixed for the next release( 0.4.3 ).

To get Rid of these until the release do the following

1. Clean your project using Build > Clean Project
2. Close your Android Studio
3. Take Backup of your project
4. Delete all .iml files inside your project
5. Delete content of .idea directory
6. Open Studio and wait until it completes the sync with gradle

Also verify if you are seeing any error in File > Project Structure . If there is any error saying "Dependency Not Added "click on that and using red bulb on right side Add them to dependency.

UPDATE

Android Studio 0.4.3 is available on Canary Channel Now.

UPDATE: @laochiv, I have found that cleaning manually the folder .idea/libraries and clicking afterward on "Sync Project with Gradle Files" solves the problem. Apparently this Sync does not remove elements, but keep the old ones and add the current ones. Probably a bug to report :)

---

I am having the same problem. However, I am using ABS directly from Maven.

dependencies {
    compile 'com.actionbarsherlock:actionbarsherlock:4.4.0@aar'
    compile 'com.android.support:support-v4:18.0.+'
}

Even the ABS Gradle Sample application marks a syntax error, although it compiles.

However, in another computer everything is working perfectly. I can not think of different conditions in each scenario.

"Does Android Studio ignore the gradle build when assessing whether something is valid syntax or not?" Yes. Android Studio imports the project configuration but runs its own compiler as you are editing and saving (you can even change it to the Eclipse ECJ compiler). The true authority on the build is Gradle, and AS is still in beta. You can try to run the gradle resync or close and reimport the project. I have had to manipulate AS like this many times, especially after making edits to build.gradle.

Edit: I have found it better to use ActionBarSherlock as a gradle dependency rather than a library directory.

compile 'com.actionbarsherlock:actionbarsherlock:4.4.0@aar'

You will need to use the SDK manager and install the local maven repository.

But it is possible to eventually get rid of these compile errors, as long as your build.gradle doesn't create any extra sourceSets that AS doesn't understand; try not to deviate too much from the android gradle plugin examples.

Also, I've been running the Canary updates of AS for the latest and greatest.