Hey there! Let's get that tip calculator crash sorted out—this is a common gotcha with input validation for numeric fields.

The Root Cause #

Your app crashes with NumberFormatException because when you enter just a . into the EditText, calling Float.parseFloat(".") throws an error (it's not a valid float value). Your existing check didn't work for two key reasons:

• You used == to compare strings (this checks reference equality, not content equality—always use .equals() for string content checks)
• Your validation logic was out of order: you tried to show a toast if the input wasn't a dot, then still proceeded to parse the input anyway. Also, you forgot to call .show() on that toast, so it never even appeared!

The Fixed Solution #

Here's how to adjust your calculate() method to properly handle empty input, just a decimal point, and valid numbers:

public void calculate() {
    float result = 0.0f;
    float totalBillResult;
    String inputText = enteredAmount.getText().toString().trim(); // Get and trim input to handle accidental spaces

    // First handle invalid cases and exit early
    if (inputText.isEmpty() || inputText.equals(".")) {
        Toast.makeText(MainActivity.this, "Please enter a valid bill amount", Toast.LENGTH_LONG).show();
        return; // Stop execution here so we don't run the crash-prone code
    }

    // If we reach here, input is valid—proceed with calculation
    try {
        enteredBillFloat = Float.parseFloat(inputText);
        NumberFormat numberFormat = NumberFormat.getCurrencyInstance(Locale.getDefault());
        
        result = enteredBillFloat * seekBarPercent / 100;
        calculatedTip.setText("Your tip will be " + numberFormat.format(result));
        
        totalBillResult = enteredBillFloat + result;
        totalBill.setText("Total bill: " + numberFormat.format(totalBillResult));
    } catch (NumberFormatException e) {
        // Safety net for any unexpected invalid input (like letters)
        Toast.makeText(MainActivity.this, "Please enter a valid number", Toast.LENGTH_LONG).show();
        e.printStackTrace(); // Optional: log the error for debugging
    }
}

Key Improvements #

• Input trimming: Added .trim() to handle accidental spaces in the input
• Early exit: We check for invalid input first and exit the method immediately, avoiding the code that would cause a crash
• Proper string comparison: Used .equals() instead of == to check for the "." input
• Toast fix: Made sure to call .show() on the toast so users actually see the error message
• Safety net: Added a try-catch block around parseFloat to catch any other unexpected invalid input that might slip through initial checks

Bonus Tip #

To reduce invalid input in the first place, set your EditText to only accept numeric input with a decimal point by adding this to your XML layout:

<EditText
    ...
    android:inputType="numberDecimal"
    android:digits="0123456789." />

This limits what users can type, making your validation even more effective.

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