Java "incompatible types" Error: Type Mismatch Explained (AP CSA)

The compiler reports incompatible types when you try to put a value of one type into a variable of another type that cannot hold it. In AP CSA this most often means assigning a double to an int, or storing the wrong object type in a typed variable.

Why students see this error

Java is statically typed: every variable has a declared type, and the compiler checks that each assignment fits. Java will automatically widen a smaller type to a larger one (int to double), but it refuses to automatically narrow a larger type into a smaller one (double to int) because that can lose data. When the assignment does not fit and no automatic conversion applies, you get incompatible types.

• Assigning a double result to an int variable without a cast.
• Storing the wrong object type, such as putting a String into an int variable.
• Forgetting that integer division and method return types must match the receiving variable.

Broken code that triggers it

public class Convert {
  public static void main(String[] args) {
    double price = 19.99;
    int rounded = price;   // incompatible types: double cannot be int
    System.out.println(rounded);
  }
}

price is a double, and the code tries to store it in an int. Narrowing a double into an int can lose the decimal part, so Java refuses to do it automatically and reports incompatible types: possible lossy conversion from double to int.

Trace: watch where it breaks

The compiler checks the type of each side of the assignment:

This is caught at compile time, so the program never runs and prints nothing. The compiler stops as soon as it finds the mismatched assignment.

The fix

public class Convert {
  public static void main(String[] args) {
    double price = 19.99;
    int rounded = (int) price;   // explicit cast: truncates to 19
    System.out.println(rounded);
  }
}

Adding the explicit cast (int) tells the compiler you intend the narrowing and accept that the decimal part is truncated (19.99 becomes 19, not 20). The reverse direction (double d = anInt;) needs no cast because widening never loses data.

How College Board tests this concept

Expect MCQs that show an assignment and ask whether it compiles. The key rule: widening (smaller to larger, like int to double) is automatic; narrowing (larger to smaller, like double to int) requires an explicit cast or it is a compile error.

Common MCQ traps (practice set)

Question 1: Does it compile?

int count = 5;
double avg = count;

Question 2: Spot the fix

This line gives incompatible types: double d = 7.5; int n = d;

Question 3: Which assignments compile?

Consider each assignment independently.

I.    double x = 5;
II.   int y = 5.0;
III.  int z = (int) 5.9;