Swift计步器数据按日期存储至Firebase数据库的实现问题

Got it, let's fix that disappearing step data issue! The problem is you're writing all your step data to the same Firebase node every day—so when the next day rolls around, you're overwriting the previous day's data instead of storing it separately.

The solution is simple: create a unique subnode for each date using a clean, Firebase-friendly date format. Here's how to implement this in your code:

1. Add a Helper Method to Generate Date Keys #

First, make a reusable function to create a consistent date string that works as a Firebase node name (no special characters like slashes). We'll use yyyy-MM-dd because it's sortable and easy to read:

private func getDateKey(for date: Date = Date()) -> String {
    let dateFormatter = DateFormatter()
    dateFormatter.dateFormat = "yyyy-MM-dd"
    // Set locale to ensure consistent formatting across regions
    dateFormatter.locale = Locale(identifier: "en_US_POSIX")
    return dateFormatter.string(from: date)
}

This method will return strings like 2024-05-20 for today's date, which is perfect for a Firebase subnode key.

2. Modify Your Step Saving Logic #

Instead of writing directly to a generic "steps" node, you'll now write to a daily_steps parent node, with each child being the date key we just created.

If your original code looked something like this (overwriting the same node):

// Original (overwrites data daily)
let stepsRef = Database.database().reference().child("steps")
stepsRef.setValue(currentStepCount)

Replace it with this to store per-date data:

// Updated (stores unique data per date)
let dateKey = getDateKey()
let dailyStepsRef = Database.database().reference().child("daily_steps").child(dateKey)

// Store both step count and a timestamp for tracking
dailyStepsRef.updateChildValues([
    "step_count": currentStepCount,
    "last_updated": Date().timeIntervalSince1970
])

Using updateChildValues instead of setValue ensures you don't overwrite existing data for the day if you save multiple times (e.g., when the app resumes). If you need to append steps instead of replacing them, you could also fetch the existing count first, add to it, then save back—just adjust based on your CoreMotion logic.

3. Fetching Historical Steps #

To retrieve steps for a specific day (like showing a history screen), use the same date key method:

func fetchSteps(for targetDate: Date) {
    let dateKey = getDateKey(for: targetDate)
    let dailyStepsRef = Database.database().reference().child("daily_steps").child(dateKey)
    
    dailyStepsRef.observeSingleEvent(of: .value) { snapshot in
        guard let stepData = snapshot.value as? [String: Any],
              let stepCount = stepData["step_count"] as? Int else {
            // No data found for this date
            print("No steps recorded for \(dateKey)")
            return
        }
        // Use the step count here (update UI, etc.)
        print("Steps on \(dateKey): \(stepCount)")
    }
}

4. Quick Firebase Rules Check #

Make sure your Firebase Realtime Database rules allow read/write access to the daily_steps node (adjust for authentication if needed):

{
  "rules": {
    "daily_steps": {
      ".read": true, // Restrict to auth users with "auth != null" if required
      ".write": true
    }
  }
}

That's it! Now every day's step data will be stored in its own subnode, so your data won't disappear when the calendar rolls over.

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