invalid_implementation_override

'{1}.{0}' ('{2}') isn't a valid concrete implementation of '{3}.{0}' ('{4}').

The setter '{1}.{0}' ('{2}') isn't a valid concrete implementation of '{3}.{0}' ('{4}').

The analyzer produces this diagnostic when all of the following are true:

• A class defines an abstract member.
• There is a concrete implementation of that member in a superclass.
• The concrete implementation isn't a valid implementation of the abstract method.

The concrete implementation can be invalid because of incompatibilities in either the return type, the types of the method's parameters, or the type parameters.

The following code produces this diagnostic because the method A.add has a parameter of type int, and the overriding method B.add has a corresponding parameter of type num:

class A {
  int add(int a) => a;
}
class B extends A {
  int add(num a);
}

This is a problem because in an invocation of B.add like the following:

void f(B b) {
  b.add(3.4);
}

B.add is expecting to be able to take, for example, a double, but when the method A.add is executed (because it's the only concrete implementation of add), a runtime exception will be thrown because a double can't be assigned to a parameter of type int.

If the method in the subclass can conform to the implementation in the superclass, then change the declaration in the subclass (or remove it if it's the same):

class A {
  int add(int a) => a;
}
class B	extends A {
  int add(int a);
}

If the method in the superclass can be generalized to be a valid implementation of the method in the subclass, then change the superclass method:

class A {
  int add(num a) => a.floor();
}
class B	extends A {
  int add(num a);
}

If neither the method in the superclass nor the method in the subclass can be changed, then provide a concrete implementation of the method in the subclass:

class A {
  int add(int a) => a;
}
class B	extends A {
  int add(num a) => a.floor();
}

Unless stated otherwise, the documentation on this site reflects Dart 3.7.3. Page last updated on 2025-05-08. View source or report an issue.