Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

141
Views
Swift - GeoFire removeObserver Not Working, seeking for workaround please

I find out that both removeObserver and .removeAllObservers() is not working in GeoFire, hoping another work around to "get out" of this observe (which keeps loading forever)

var newRefHandle: FIRDatabaseHandle?
var gFCircleQuery: GFCircleQuery?

func findFUsersInOnePath(location: CLLocation,
                         radius: Int,
                         indexPath: String,
                         completion: @escaping () -> ()){
    var ids = 0
    let geofireRef = usersRef.child(indexPath)
    if let geoFire = GeoFire(firebaseRef: geofireRef) {
        gFCircleQuery = geoFire.query(at: location, withRadius: Double(radius))
        newRefHandle = gFCircleQuery?.observe(.keyEntered, with: { (key, location) in
            // if key fit some condition then perform some other firebase call to other database(async), afterwards:
            ids += 1
            if (ids >= 3) {
                //RemoveObersver not working below...
                self.gFCircleQuery?.removeObserver(withFirebaseHandle: self.newRefHandle!)
                completion()
            }
        })
        //I find that observeReady gets call right away despite we haven't complete  code above 
        gFCircleQuery?.observeReady({
            completion()
        })
}
over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

My guess is that you're still getting some .keyEntered events after the call to removeObserver, which is actually to be expected.

GeoFire performs a single query to get all keys within the range for your query, and then calls your .keyEntered callback for each of these keys. Even if you call removeObserver for the first key, GeoFire will continue to call the .keyEntered callback with the remainder of the keys that it already got from the database.

For this reason, I'd recommend removing the observer inside the ready block for the query. The behavior will not change when you do that, but it'll make more sense as that ready block is called when GeoFire is done telling you about the batch of keys.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!