How to Fix NullPointerException in Java

1. Calling a Method Before Creating the Object

This is the most common beginner mistake.

Student student = null;
System.out.println(student.getName());

Fix:

Student student = new Student("Ava");
System.out.println(student.getName());

The variable student needs a real Student object before Java can call getName().

2. A Method Returns Null

A method can return null when no matching record exists.

Student student = findStudentById(42);
System.out.println(student.getName());

Fix:

Student student = findStudentById(42);
if (student == null) {
System.out.println("Student not found");
return;
}
System.out.println(student.getName());

This pattern appears in search, login, menu, inventory, library, and banking assignments.

3. An Array Exists but Its Objects Do Not

Creating an object array creates the slots, not the objects inside the slots.

Student[] students = new Student[3];
System.out.println(students[0].getName());

students exists. students[0] is still null.

Fix:

Student[] students = new Student[3];
students[0] = new Student("Ava");

System.out.println(students[0].getName());

This mistake appears often in first-semester Java assignments because arrays of primitives and arrays of objects behave differently.

4. HashMap.get() Returns Null

HashMap.get(key) returns null when the key does not exist.

Map<Integer, Student> students = new HashMap<>();

Student student = students.get(42);
System.out.println(student.getName());

Fix:

Student student = students.get(42);

if (student == null) {
System.out.println("No student found for ID 42");
return;
}

System.out.println(student.getName());

Use containsKey() when a stored value can also be null.

if (students.containsKey(42)) {
Student student = students.get(42);
}

This issue appears in assignments that use HashMap, TreeMap, lookup tables, student records, product IDs, or account numbers.

5. File Input Has a Missing Value

Java code often fails when a text file, CSV file, or user input does not contain the value your code expects.

String email = userData.get("email");
System.out.println(email.toLowerCase());

Fix:

String email = userData.get("email");

if (email == null || email.isBlank()) {
System.out.println("Email is missing");
return;
}

System.out.println(email.toLowerCase());

Hidden grading tests often include missing fields, blank strings, empty files, and unusual input order. Code that passes your sample file can fail on the grader.

6. Long Method Chains Hide the Null Object

Long chains make the null source harder to see.

System.out.println(order.getCustomer().getAddress().getCity());

Break the chain while debugging.

Customer customer = order.getCustomer();

if (customer == null) {
System.out.println("Customer is missing");
return;
}

Address address = customer.getAddress();

if (address == null) {
System.out.println("Address is missing");
return;
}

System.out.println(address.getCity());

This version is longer, but it shows the exact missing object. After the bug is fixed, keep the guards when missing data is a valid case.

7. A Constructor Does Not Set Required Fields

An object can be created and still contain null fields.

public class Student {
private String name;

public Student() {
}

public String getName() {
return name;
}
}

This code compiles, but name remains null.

Fix:

public class Student {
private final String name;

public Student(String name) {
this.name = Objects.requireNonNull(name, "name cannot be null");
}

public String getName() {
return name;
}
}

This fix prevents invalid Student objects from being created.