Memory Leaks issue using .whereField(_, isEqualTo:)

[holmeso983]

Description

The Issue

I'm currently receiving mutiple memory leaks when using the .whereField(, isEqualTo:) in one of my functions. The happens no where else in my code other than here, which is quite confusing. When I remove just the .whereField(, isEqualTo:) line, I have no issues.

The Code:

static func getManyFromProject(_ project: Project, topLevelCategoryID: String?, sortByDateAdded: Bool = false, limit: Int = 10) async -> Result<[InventoryItem], Error> {
        do {
            // 1. Base query setup for project items
            var baseQuery: Query = FirebaseService.shared.database
                .collection("companies")
                .document("123456")
                .collection(Collections.inventory.rawValue)
            // Apply project filter
                .whereField("projectID", isEqualTo: project.objectID)   // MARK: MEMORY LEAK HERE
            
            // Execute the base query
            let allProjectItems: [InventoryItem] = try await FirebaseService.shared.getMany(with: baseQuery).get()
 
            return .success(allProjectItems)
        } catch let error {
            return .failure(error)
        }
    }

Logs

Reproducing the issue

No response

Firebase SDK Version

10.23.1

Xcode Version

15.3

Installation Method

Swift Package Manager

Firebase Product(s)

Database, Storage

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[jesus-mg-ios]

Yas, Same error here, workaround trying to not use whereField ...

[MarkDuckworth]

Thanks for the report and the sample code. I'm going to close this as a duplicate of #12613. The team is working on a fix, but I will also share this report.