Error : Ambiguous method call. Both findViewById (

Question

I am getting the error: "Ambiguous method call" on initializing Toolbar using Android Studio 3.0 RC1. I have extended my Activity with AppCompatActivity and compiling my application using 'compileSdkVersion 26'. Attaching a screenshot of the error.

Answer 1

I have recently upgraded to build tools version 27.0.2 and faced the same problem. But noticed that I had the compileSdk version set to 25. Changing compileSdk to 27 resolved the issue.

Answer 2

For me, it was the compileSdkVersion which was different than the support libraries used

Answer 3

For me changing build tool version to 27.0.2 worked, given that all your other dependencies are API 27 as well.

buildToolsVersion '27.0.2'

Answer 4

This can suddenly appear when running a code analyzer like FindBugs-IDEA. A quick way to clear the warning is to temporarily change the buildToolsVersion in your app/build.gradle then change it back again.

For example, follow these steps:

1. Open your app/build.gradle file.
2. Change buildToolsVersion to '26.0.1' then sync project (press the 'Sync Now' button when it appears at the top)
3. Change the buildToolsVersion back to whatever you had before.
4. Press the 'Sync Now' button

This should clear the error.

Answer 5

First make sure that you have no transitive dependencies that are using older support libraries. Run the following command and make sure that no older support libraries are in use.

gradlew :app:dependencies

Make sure that your gradle file is updated with latest dependencies. eg: compileSdkVersion 27, targetSdkVersion 27, buildToolsVersion 27.0.3. etc. It would also benefit to make sure that non of your app flavors have been using a custom targetSdkVersion.

Ctrl + click on the findViewById method. It will show you the 2(perhaps more?) conflicting methods. In my case the conflict was between the findViewById method from API 23 and API 27. Therefore I had to remove the SDK and sources for Android version 23. Once I removed it and did Invalidate Caches/Restart it solved my problem.

Answer 6

Maybe you have difference between compileSdkVersion and targetSdkVersion