Android Studio lint reports “cannot infer argument types.”

I have reviewed the Inspection report for my project that is provided by Android Studio after having executed the following command:

Analyze->Inspect Code...

The report indicates a problem with this code snippet in my file:

  • android maps: How to Long Click a Map?
  • set loadURLTImeOutValue on webview
  • Relative Layout. Between 2 items
  • Full queue, lose event in Android Emulator
  • How to set bold title in Action Bar?
  • Android SpeechRecognizer “confidence” values are confusing
  • buildTypes {
        release {
            runProguard false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.txt'
            signingConfig signingConfigs.release

    The specific problem is cannot infer argument types (at line 34). I have included a snapshot for clarity.

    Android Studio lint Inspection complaint

    One SO answer seems to suggest this is just a bogus warning. If that is the case, can I safely suppress this warning?

    Related posts:

    Can PackageManager.getInstallerPackageName() tell me that my app was installed from Amazon app store...
    Android Sqlite get last insert row id
    Android Emulator for windows?(Not to install the Complete SDK, Just Emulator Needed)
    ListFragment how to get the listView?
    Java.exe finished with non-zero exit value 2 in Android Studio
    Drag & Drop without removal from owner
  • Workaround mapping between NetworkInfo and NetworkInterface
  • NoClassDefFoundError:
  • Android 4.0 Sub-Title (section) Label Styling
  • Set selected item in Android BottomNavigationView
  • Points to remember while testing android application
  • How to get charles proxy work with Android 7 nougat?
  • One Solution collect form web for “Android Studio lint reports “cannot infer argument types.””

    You can (very likely) safely ignore this warning. The IntelliJ (Android Studio) Groovy inspection is decent, but far from perfect. I have several advanced Gradle build scripts that are riddled with these and other inspection errors, although everything runs correctly. However, there is a chance you make a programming error and the inspection is technically correct, but you’ll find that out once you attempt to execute your build script.

    For this particular warning, you can turn it off on a by-line basis by using

    //noinspection GroovyAssignabilityCheck

    You can also turn it off entirely by going to File > Settings > Inspections and type Incompatible type assignments in the filter box and uncheck that inspection option. There you can also configure all the Groovy inspection options if you want to turn off others as well.

    Android Babe is a Google Android Fan, All about Android Phones, Android Wear, Android Dev and Android Games Apps and so on.