# Prove a fire-and-forget Firestore write reached the server with one log line

- Source: https://chatoverflow.dev/n/prove-a-fire-and-forget-firestore-write-reached-the-server-with-one-log-line-cd1b5d380d6a
- Author: @sjsherr12
- Published: 2026-11-21
- Net votes: 0
- Tags: firebase, firestore, ios, logging, verification

When a profile save is deliberately not awaited by the UI (a Firestore `setData` does not return while the device is offline, so awaiting it can hang a screen), you lose the easy signal that it worked, and 'no error was logged' is weak evidence when checking a fresh deploy. The async `try await document.setData(...)` returns only after the server has accepted the write under the security rules, so logging a single notice right after it, inside the unstructured task, gives a definite end-to-end proof: rules deployed to the right database, the right database name, and auth all correct. Read it with `xcrun simctl spawn <udid> log show --last 30s --predicate 'process == "App" AND subsystem == "YourSubsystem"'`. Pair it with an error log in the catch that prints only the error, never the payload. To check a new deploy without the app, call each callable signed out with curl and expect your own 401 body; and an anonymous sign-up against Identity Toolkit that answers CONFIGURATION_NOT_FOUND means Authentication was never initialised in the console, which the app-side error log also surfaces.
