100

I'm getting error in Kotlin in this part:

class GitHubRepoAdapter(
    private val context: Context,
    private val values: List<GithubRepo>
) : ArrayAdapter<GithubRepo>(
    context, 
    R.layout.list_item,
    values
)

private val context: Context

In the log it says:

Error:(14, 25) Accidental override: The following declarations have the same JVM signature
(getContext()Landroid/content/Context;):  
    fun <get-context>(): Context  
    fun getContext(): Context!

I'm not able to see what is causing the problem.

iknow
  • 8,358
  • 12
  • 41
  • 68
Ege Kuzubasioglu
  • 5,991
  • 12
  • 49
  • 85
  • 1
    May be this would be helpful https://stackoverflow.com/questions/29268526/how-to-overcome-same-jvm-signature-error-when-implementing-a-java-interface/35471596 – Ilya Serbis Feb 08 '19 at 11:09

7 Answers7

126

This happens because the Kotlin compiler tries to generate a getter for val context declared in your class primary constructor, namely a method getContext(), but the base class ArrayAdapter<T> already has such a method.

You can solve that by doing one of the following:

  • Change your class' constructor parameter not to be a val.

       class GitHubRepoAdapter(context: Context, ...

    In this case, the getter won't be generated, and the conflict will be gone.

    This seems to be the preferrable solution in your case, because, even without redeclaration, there is already a synthetic property context inferred from the Java getter.

  • Use the @JvmName annotation, apply it to the context property getter:

       class GitHubRepoAdapter(@get:JvmName("getAdapterContext") private val context: Context, ...

    This will make the compiler generate the getter with another JVM name (the one specified in the annotation), thus avoiding the conflict, but making accessing it from Java less intuitive (especially since there will be two similar functions). In Kotlin, you will still be able to use the property with its original name context.

hotkey
  • 140,743
  • 39
  • 371
  • 326
  • 2
    Is this working with val properties inherited from interface? I mean for example interface with `val context: Context`? – Karol Kulbaka Dec 18 '18 at 10:50
42

In addition to the answer already given...

  • Or, you can keep val (or var) but change the name of the parameter to something that doesn't collide with the super class declaration.

In a class declaration, the parameters in the constructor declarations are often more than just parameters. Using val or var, you are actually declaring property members (not just parameters). And along with the property members come automatic "getters" (and "setters" in the case of var). The automatic getter, in the OP's case, is called getContext() but the base class already has a getContext() (same signature).

Most likely, the intent here was to just pass the context to the super, in which case, the other answer works best. But, in the case where a new property is desired, but the name chosen collides with a differently purposed member of the super, changing the name is the alternative.

In short, changing the name applies when you do want a new member variable but a super class already exposes a different member by the same name.

Les
  • 10,335
  • 4
  • 40
  • 60
  • I think this version is actually more preferable to the accepted answer. If my super class already has a property/getter/setter for a variable, why would I create a 2nd one at all? Removing `val/var` seems the slickest way to go for sure. – withoutclass Jul 28 '17 at 16:55
  • @withoutclass - you misunderstand my answer, mine actually says you can keep the val or var and just change the name of the variable, which is useful when the super class already uses the first name you chose. In the case where the super class uses the name for a property with an entirely different purpose than what you were planning for your variable, then a new property is appropriate using a different name. I will update my answer to make it more clear. – Les Jul 28 '17 at 19:53
  • Best and simple answer unlike others. – Talha Safdar Dec 17 '22 at 01:57
4

Change variable name to myContext and will work with you without any problems.

Hamdy Abd El Fattah
  • 1,405
  • 1
  • 16
  • 16
3

I got a similar error I solved it by removing the null checks from the constructor parameter

From

fun onChildDraw(
    c: Canvas?,
    recyclerView: RecyclerView?,
    viewHolder: RecyclerView.ViewHolder,
    dX: Float,
    dY: Float,
    actionState: Int,

To

fun onChildDraw(
    c: Canvas,
    recyclerView: RecyclerView,
    viewHolder: RecyclerView.ViewHolder,
    dX: Float,
    dY: Float,
    actionState: Int,
m'hd semps
  • 564
  • 4
  • 14
  • 1
    The opposite worked for me. I suppose the full answer is that the types have to be the same whether they include or exclude null checks. – petestmart Feb 01 '23 at 18:46
1

I would like to add something here:

When you name your parameter as context it will collide with the base class parameter name which is also context by default. So changing the name of your parameter will help you.

R. Rohilla
  • 71
  • 8
1

The return types of the two functions are Context and Context! which are two different things. To fix it, add the exclamation mark to your code.

helvete
  • 2,455
  • 13
  • 33
  • 37
Ian Moses
  • 11
  • 2
0

Had similar problems, what worked was ensuring that my targetSdkVersion and compileSdkVersion were the same across all modules.

yevbe
  • 1
  • 1