Hey there, let's break down why you're hitting this null pointer exception and how to fix it quickly.

The Root Cause #

The error message clearly points to the db object in your login.java being null when you call db.checkEmail(user_email_id). Even though your checkEmail method itself looks mostly fine, you're trying to call a method on an uninitialized instance of databaseHelper. That's exactly what triggers this crash.

Step-by-Step Fixes #

1. Properly Initialize the databaseHelper Instance in login.java

You need to create a valid instance of databaseHelper before using it. Make sure you pass a valid Context (like your Activity's this reference) when initializing it. Update your login code like this:

// Add this line before calling checkEmail (best placed in your Login Activity's onCreate() method)
databaseHelper db = new databaseHelper(this); 

Boolean emailExists = db.checkEmail(user_email_id);
if(emailExists) {
    // Your existing logic here
}

• Double-check that you're initializing db inside a valid lifecycle method (like onCreate()) and not in a static context or before the Activity is fully created.

2. Verify Your databaseHelper Constructor

Ensure your databaseHelper class correctly extends SQLiteOpenHelper and has a valid constructor. Missing this can break instance creation entirely:

public class databaseHelper extends SQLiteOpenHelper {
    // Define your database details
    private static final String DB_NAME = "user_database.db";
    private static final int DB_VERSION = 1;

    public databaseHelper(Context context) {
        super(context, DB_NAME, null, DB_VERSION);
    }

    // Required override methods for SQLiteOpenHelper
    @Override
    public void onCreate(SQLiteDatabase db) {
        // Create your user table here (example query)
        db.execSQL("CREATE TABLE user (id INTEGER PRIMARY KEY AUTOINCREMENT, email TEXT UNIQUE)");
    }

    @Override
    public void onUpgrade(SQLiteDatabase db, int oldVersion, int newVersion) {
        // Handle database upgrades if needed
        db.execSQL("DROP TABLE IF EXISTS user");
        onCreate(db);
    }

    // Updated checkEmail method with cleanup
    public Boolean checkEmail(String email) {
        SQLiteDatabase db = this.getReadableDatabase();
        Cursor cursor = db.rawQuery("Select * from user where email=?", new String[]{email});
        boolean hasMatch = cursor.getCount() > 0;
        
        // Critical: Close the cursor to avoid memory leaks
        cursor.close();
        // Optional: Close the database if you don't need it for further operations
        db.close();
        
        return hasMatch;
    }
}

3. Clean Up Cursor Usage

In your original checkEmail method, you weren't closing the Cursor after using it. This can cause memory leaks over time, so adding cursor.close() is an important best practice (as shown above).

Why Did It Work Before? #

Chances are, you had code to initialize the db instance in login.java that got removed accidentally, or you were testing with a different setup where the db object was already properly initialized.

内容的提问来源于stack exchange，提问作者Umang