Skip to content

docs(delete-user-data): note that a failed event publish doesn't stop deletion #3321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CorieW merged 1 commit into from
Nov 10, 2026
Merged

docs(delete-user-data): note that a failed event publish doesn't stop deletion #3321

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions kits/delete-user-data/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -336,6 +336,13 @@ The Firebase CLI now sets it to the function that published the event
so it differs between `clearData`, `handleSearch` and `handleDeletion`. If your
event triggers filter on `source`, filter on the event `type` instead.

### A failed event publish doesn't stop deletion

If an event can't be published, the kit logs a warning and carries on deleting.
The extension failed the function instead: in `clearData`, auto-discovery and
`SEARCH_FUNCTION` were skipped, so their data was left behind, and
`handleSearch` and `handleDeletion` failed after deleting.

### Unchanged

Event types and payloads are the same. The functions still publish
Expand Down
Loading