Documentation says you need to call observeEventType:withBlock
to remove an observer if you no longer need it.
I've seen samples where it is called within ViewDidDisAppear
. I also find some Obj-C code called this method within deinit
, which is not ncessary in Swift.
In my simple app, however, I want data to be synced as long as I am in the app. If this is the case, do I have to call observeEventType:withBlock
ever?
I checked the Chat-Swift sample code on Firebase website, and did not find observeEventType:withBlock
.
Does it mean it's ok not to call observeEventType:withBlock
:. if I want the observer to be on when the app is in use?
Thank you.
UPDATE
Thanks to Jay and David. I see it makes sense to observe in ViewWillAppear and remove it in ViewDidDisappear.
However, I am using observeEventType to monitor any value change to the node and would update UI if there is any. If i put it in ViewWillAppear:
override func viewWillAppear(animated: Bool) {
super.viewWillAppear(animated)
ref.observeEventType(.Value, withBlock: { snap in {
// **update UI if there is any Value change**
})
}
The problem with putting it in viewWillAppear
is that, it gets called every time the view appears, regardless of Value change or not. Because of this, the snapshot is downloaded and my UI gets refreshed every time I return to the view. This becomes counterproductive.
I have also tried ChildAdded
/ChildRemoved
, however, it only returns the last node, not the path from my ref:
For instance, if I add to ref/child1/child2/child3/value, ChildAdded
would only return child3/value.
So if I have to observe Value, it seems like putting it in ViewDidLoad
is better? In this way, it gets the snapshot one time when the view loaded, and would repeat whenever there is a change, but would not obtain the snapshot just because the view appears.
See Question&Answers more detail:
os