Java "variable might not have been initialized" Error (AP CSA)

This compiler error means you tried to use a local variable before it was definitely given a value. Java refuses to read a local variable that might still be unassigned, so the fix is to make sure it has a value on every path before you use it.

Why students see this error

Unlike instance fields, which default to 0, false, or null, local variables have no default value. The compiler tracks whether a local variable is definitely assigned before each use. If there is any path where it might still be unassigned, the compiler reports variable might not have been initialized rather than risk reading garbage.

• Declaring a local variable and using it before assigning a value.
• Assigning a value only inside an if, then using the variable after, where the else path leaves it unassigned.
• Assigning only inside a loop that might run zero times.

Broken code that triggers it

public static void main(String[] args) {
  int result;          // declared, not initialized
  int score = 70;
  if (score >= 90) {
    result = 1;       // only assigned on this path
  }
  System.out.println(result);   // result may be unassigned
}

result is only assigned when score >= 90. Since score is 70, and more importantly since the compiler sees a path where the if is false and result stays unassigned, it refuses to let you print result and reports the error.

Trace: watch where it breaks

The compiler tracks definite assignment on every path:

The compiler does not care that score happens to be 70 here; it reasons about all possible paths. As long as one path leaves result unassigned before use, it is an error.

The fix

public static void main(String[] args) {
  int result = 0;       // initialize at declaration
  int score = 70;
  if (score >= 90) {
    result = 1;
  }
  System.out.println(result);   // always has a value now
}

Initializing result to 0 at declaration guarantees it has a value on every path. Alternatively, add an else that assigns it, so both branches define it before use.

How College Board tests this concept

A key exam distinction: instance fields are auto-initialized to defaults, but local variables are not. MCQs may contrast a field that defaults to 0 with a local variable that must be explicitly assigned, testing whether you know which is which.

Common MCQ traps (practice set)

Question 1: Field vs local

Question 2: Which compile?

Each shows a local int n used in a println.

I.    int n = 0; if (x>0) n = 1; print(n);
II.   int n; if (x>0) n = 1; print(n);
III.  int n; if (x>0) n = 1; else n = 2; print(n);

Question 3: Best fix

A local variable is assigned only inside a for loop that might run zero times, then used after.