Java "missing return statement" Error and How to Fix It (AP CSA)

The compiler reports missing return statement when a method that promises to return a value has a path through it that reaches the end without returning anything. In AP CSA this usually means a return is buried inside an if with no return for the else path.

Why students see this error

If a method's header declares a return type (like int or boolean), the compiler insists that every path through the method returns such a value. If a return only happens inside an if, the compiler sees a path where the condition is false, no return runs, and the method falls off the end with nothing to give back. That path is the error.

• A return inside an if with no return for the case where the condition is false.
• Returning inside a loop only, so a method with an empty loop has no return.
• Forgetting a final return after a chain of if statements.

Broken code that triggers it

public static String sign(int n) {
  if (n > 0) {
    return "positive";
  }
  if (n < 0) {
    return "negative";
  }
  // no return when n == 0 -> missing return statement
}

The method returns a String when n > 0 or n < 0, but there is no return for the case n == 0. The compiler sees that path reach the closing brace with nothing returned, so it reports missing return statement.

Trace: watch where it breaks

The compiler checks whether every path returns a value:

The compiler does not need a particular input to fail; it reasons about all paths. Because the n == 0 path exists and does not return, the build fails before any execution.

The fix

public static String sign(int n) {
  if (n > 0) {
    return "positive";
  }
  if (n < 0) {
    return "negative";
  }
  return "zero";   // covers the remaining path
}

Adding a final return "zero"; guarantees the n == 0 path returns a value, so every path now ends in a return. A common alternative is to use if/else if/else so the compiler can see the cases are exhaustive.

How College Board tests this concept

On free-response questions, a method that fails to return on some path can cost points even if the logic is otherwise right. MCQs may show a method with a return only inside an if and ask why it does not compile; the answer is the uncovered path.

Common MCQ traps (practice set)

Question 1: Why no compile?

public static int f(boolean b) {
  if (b) {
    return 1;
  }
}

Question 2: Which compile?

Each method declares a return type of int.

I.    if (x>0) return 1; else return -1;
II.   if (x>0) return 1; return -1;
III.  if (x>0) return 1;

Question 3: Best fix

A method returning boolean returns true inside a loop when it finds a match, but otherwise nothing.