Home » Android » Android Studio – Ambiguous method call getClass()

Android Studio – Ambiguous method call getClass()

Posted by: admin March 11, 2020 Leave a comment

Questions:

I’m using Android Studio for my Android application.
My code works and compiles.
Recently, the IDE showes me error (red lines) on getClass of the following code:

fragment.getClass().getSimpleName()

But still the application compiles and runs.
The error is:

Ambiguous method call. Both
getClass () in Object and
getClass () in Object match.

Can some one explain me what is it about? and why the code still running?

How to&Answers:

I think it is a bug in Android Studio. As we know, Android Studio is based on the IntelliJ Platform and the existing functionality of IntelliJ IDEA Community Edition.

Google has developed it in cooperation with JetBrains. And same bug is reported to happen in IntelliJ as well.
Have a look at the Error report

The only workaround to this issue is to cast the instance you call getClass() on, to Object as follows:

((Object) this).getClass()

Answer:

Rather than modify your application code, you can avoid this bug by patching your Android SDK’s source code.

When you come across the getClass() error, go to the declaration of the method (⌘B on Mac). This will navigate to a path such as $ANDROID_HOME/sources/android-20/java/lang/Object.java. Now, within IntelliJ or Android Studio:

  • Make Object.java writable by choosing File -> Make File Writable. You may be prompted to do this automatically if you try to edit the file.
  • Remove the unbounded wildcard:

    // Removed unbounded wildcard (Class) to avoid http://youtrack.jetbrains.com/issue/IDEA-72835
    public final native Class getClass();

Newer versions of Android Studio appear to suffer from a bug which prevents you from editing the file even after declaring it as writable. Instead, copy the path, Edit -> Copy Path or ⇧⌘C, and edit it in your favorite editor.

This change will preserve source navigation functionality. Other options:

  • You may comment out the entire getClass() declaration.
  • You may append a non-Java extension to the name of the Object.java file, e.g. Object.java.in.

Answer:

Cast your “getClass” to an Object, use

((Object) this).getClass()

For those having this problem with fragments, use

((Object) fragment).getClass()

Answer:

First of all the related Android Studio issue is here.
Please star it so it can get some attention!

Also the related IntelliJ issue is here.

A good workaround for this is to rename <sdk>/android-<platform>/java/lang/Object.java to Object.java.XXX for instance. This will prevent AS from seeing it and the issue will be avoided. Of course by doing this, you can no longer easily navigate to the source of Object from within AS.

You can rename the file back to its original name when this bug will be fixed…

Answer:

Today I ran into the same problem when I created a new project. I compared to another project which did not have this problem and found one difference. The old project was built against “Android 4.2.2” while the new one was by default set to “Android API 19 Platform”. I changed that to “Android 4.2.2” which equals API 17 and the red error marker vanished. API 17 is sufficient for my project so I can leave it this way. I have no idea why this resolves the problem, to be honest.

Answer:

I found a fix for this, at least on my end. It’s definitely an IntelliJ bug, but it seems to be caused by a conflict between the classes in the sourcepath and in the classpath for the Android SDK.

If you go to Project Structure > SDKs > {{Your Android SDK}}, remove any Android entries from the Sourcepath tab. The problem with this workaround is that you no longer have direct access to sources from within IntelliJ/Android Studio.

I’ve posted the same information on the Jetbrains issue tracker, so hopefully we’ll see a fix soon.

Answer:

Just use fragment.class.getSimpleName();