如何通过自动生成的文档ID删除Firestore中的文档？

Hey there! Let's work through that deletion issue you're facing with your Firestore-powered Android rental app. It sounds like you're on the right track—using the auto-generated document ID is the correct approach, so let's break down where things might be going wrong and how to fix it.

Step 1: Make Sure the Document ID is Properly Passed to the Detail Activity #

First up, you need to ensure the auto-generated document ID travels from your RecyclerView item to the detail page when the user taps it. Here's how to handle that:

In your RecyclerView Adapter #

When setting up the click listener for each item, grab the document ID from your data model (you should be storing this when fetching the list!) and pass it via an Intent:

holder.itemView.setOnClickListener(v -> {
    // Assume your data model has a getDocId() method to retrieve the stored ID
    String propertyDocId = propertyList.get(position).getDocId();
    Intent detailIntent = new Intent(v.getContext(), PropertyDetailActivity.class);
    detailIntent.putExtra("PROPERTY_DOC_ID", propertyDocId);
    v.getContext().startActivity(detailIntent);
});

In your Property Detail Activity #

Retrieve the document ID from the Intent when the activity starts:

private String propertyDocId;

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

    // Grab the document ID passed from the RecyclerView
    propertyDocId = getIntent().getStringExtra("PROPERTY_DOC_ID");
    
    // Set up your delete button click listener next...
}

Pro Tip: Double-check that you're storing the document ID in your data model when fetching the list from Firestore. If you skip this step, you won't have the ID to pass along! Here's how to do that during the initial fetch:

FirebaseFirestore db = FirebaseFirestore.getInstance();
db.collection("properties") // Replace with your actual collection name
    .get()
    .addOnCompleteListener(task -> {
        if (task.isSuccessful()) {
            List<Property> propertyList = new ArrayList<>();
            for (QueryDocumentSnapshot doc : task.getResult()) {
                Property property = doc.toObject(Property.class);
                // Store the auto-generated document ID in your model
                property.setDocId(doc.getId());
                propertyList.add(property);
            }
            // Update your RecyclerView adapter with the list
        }
    });

Step 2: Implement the Delete Function with Firestore #

Once you have the correct document ID in the detail activity, setting up the delete button is straightforward. Here's the code for the button click listener:

Button deleteButton = findViewById(R.id.btn_delete_property);
deleteButton.setOnClickListener(v -> {
    if (propertyDocId == null || propertyDocId.isEmpty()) {
        Toast.makeText(this, "Invalid property ID", Toast.LENGTH_SHORT).show();
        return;
    }

    FirebaseFirestore db = FirebaseFirestore.getInstance();
    db.collection("properties") // Use your actual collection name here
        .document(propertyDocId)
        .delete()
        .addOnSuccessListener(aVoid -> {
            // Success: Notify user and navigate back to the list
            Toast.makeText(this, "Property deleted successfully", Toast.LENGTH_SHORT).show();
            finish(); // Close the detail activity to return to RecyclerView
        })
        .addOnFailureListener(e -> {
            // Failure: Log the error and notify user
            Log.e("FirestoreDelete", "Failed to delete property", e);
            Toast.makeText(this, "Delete failed. Please try again.", Toast.LENGTH_SHORT).show();
        });
});

Step 3: Check Firestore Security Rules #

A common gotcha is forgetting to update your Firestore security rules to allow deletion. If your app restricts deletion to the property owner, your rules might look like this:

match /properties/{propertyId} {
    allow delete: if request.auth != null && request.auth.uid == resource.data.ownerUid;
}

If you're testing, you can temporarily set more permissive rules (but don't leave them this way for production!):

match /properties/{propertyId} {
    allow delete: if request.auth != null;
}

Quick Troubleshooting Checks #

• Verify the Document ID: Print propertyDocId to Logcat and compare it to the ID shown in your Firestore console—make sure they match exactly.
• Network Connection: Firestore deletion requires an active network connection (offline deletion will sync once connectivity is restored, but testing with a live connection avoids confusion).
• Data Model Setup: Ensure your Property class has a docId field with getters and setters so you can store and retrieve the ID correctly.

Give these steps a shot, and you should have that deletion functionality working in no time!

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