Hey there, let's dig into that dice display bug you're hitting—super frustrating when it works sometimes but randomly vanishes, right? Since this only happens when launching the second Activity via your Spinner, let's break down the most likely culprits and how to fix them.

1. First, Check Intent Data & Random Value Handling #

The most common issue here is that the dice value being passed to the second Activity isn't consistent, or the random number generation has a flaw.

• Verify Intent Extras: In your second Activity's onCreate, add a log statement to print the dice value you're receiving. Sometimes, when Spinner events fire unexpectedly (like on initial load), you might be sending a default or invalid value that maps to no image.
• Fix Random Number Range: Make sure your random number generates a value between 1 and your dice's maximum faces (e.g., new Random().nextInt(6) + 1 for a 6-sided die). If you forget the +1, you'll get a 0 sometimes, which probably doesn't have a corresponding image resource.

2. Spinner Event Listener Gotchas #

Spinner's onItemSelected can fire more often than you expect—like when the Activity first loads, or when the user selects the same item twice. This can lead to duplicate Intent launches or stale data being sent.

• Filter Initial Trigger: Add a boolean flag (e.g., isFirstLaunch) to skip the first onItemSelected call that happens when the Spinner initializes. That way, you only launch the Activity when the user intentionally selects an item.
• Avoid Duplicate Intents: Check if the selected position is different from the last one before sending the Intent. This prevents redundant launches that might cause data confusion.

3. Image Resource Mapping & Loading #

If the dice value is correct but the image still disappears, the problem might be with how you're mapping values to drawables.

• Validate Resource IDs: Double-check that every possible dice value maps to an existing drawable. A typo in the resource name (like dice_one instead of dice_1) will result in a 0 resource ID, which makes the ImageView show nothing.
• Add Fallback Image: In your switch/case for mapping values, add a default case that sets a placeholder or error image. This way, if an invalid value slips through, you'll see the placeholder instead of a blank screen.
• Check ImageView Visibility: Ensure your ImageView's visibility isn't being accidentally set to GONE or INVISIBLE somewhere in your code—maybe in a lifecycle method or error handling block.

4. Activity Lifecycle & State Restoration #

Sometimes, when the second Activity is recreated (e.g., after rotating the screen or the system reclaims memory), the dice state isn't saved, leading to a blank image.

• Save & Restore State: Override onSaveInstanceState to save the current dice value, then restore it in onRestoreInstanceState or onCreate (using the savedInstanceState bundle). This ensures the dice image stays consistent even if the Activity is recreated.

Example Code Snippets #

Here's how to implement some of these fixes:

Main Activity Spinner Handling

private boolean isFirstSpinnerLaunch = true;

// Inside your onCreate or where you set up the Spinner
spinner.setOnItemSelectedListener(new AdapterView.OnItemSelectedListener() {
    @Override
    public void onItemSelected(AdapterView<?> parent, View view, int position, long id) {
        // Skip initial load trigger
        if (isFirstSpinnerLaunch) {
            isFirstSpinnerLaunch = false;
            return;
        }

        // Generate valid dice value (1-6 for 6-sided die)
        int diceValue = new Random().nextInt(6) + 1;
        Intent intent = new Intent(MainActivity.this, DiceActivity.class);
        intent.putExtra("DICE_VALUE", diceValue);
        startActivity(intent);
    }

    @Override
    public void onNothingSelected(AdapterView<?> parent) {
        // No action needed here
    }
});

Second Activity Image Setup & State Restoration

@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_dice);

    ImageView diceImageView = findViewById(R.id.dice_image);
    int diceValue = getIntent().getIntExtra("DICE_VALUE", 0);

    // Log to verify the value
    Log.d("DiceActivity", "Received dice value: " + diceValue);

    // Map value to image resource
    int diceImageRes = getDiceDrawableRes(diceValue);
    diceImageView.setImageResource(diceImageRes);
    diceImageView.setVisibility(View.VISIBLE);

    // Restore state if Activity was recreated
    if (savedInstanceState != null) {
        int savedValue = savedInstanceState.getInt("SAVED_DICE_VALUE", 0);
        diceImageView.setImageResource(getDiceDrawableRes(savedValue));
    }
}

@Override
protected void onSaveInstanceState(Bundle outState) {
    super.onSaveInstanceState(outState);
    int diceValue = getIntent().getIntExtra("DICE_VALUE", 0);
    outState.putInt("SAVED_DICE_VALUE", diceValue);
}

private int getDiceDrawableRes(int diceValue) {
    switch (diceValue) {
        case 1: return R.drawable.dice_1;
        case 2: return R.drawable.dice_2;
        case 3: return R.drawable.dice_3;
        case 4: return R.drawable.dice_4;
        case 5: return R.drawable.dice_5;
        case 6: return R.drawable.dice_6;
        default: return R.drawable.dice_default; // Fallback image
    }
}

Start by adding the log statements to see exactly what's being passed to the second Activity—that'll help you narrow down whether the issue is with data transfer, resource mapping, or Spinner events. Let me know if you hit any snags with these steps!

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