In the handleSelectPhoto() function ?

It seems to be an issue related to removing of the observer in the viewWillDisappear, when commented out it solves the issue. Im assuming that when the image picker opens it counts as a viewwilldissapear ?

thx

thx m8

wow .. that was very quick response... thank you very much

Thanks bro, The reason was removeObserver in viewWillDisappear so,I moved setupNotificationObserver() to viewWillAppear() It works perfectly!

storageReference.downloadURL(completion: { (imageLink, err) in if let err = err { print(err.localizedDescription) return } ... })

Hi, thanks Brian. Tried scrollView now and keyboard only goes up tu the active field, covering the ones below...mmm, it was nicer with the stack view with keyboard stuck below the buton, i've been trying to marry the 2 methods together somehow, the stackview on top of the scrollview or just the scrollview in the bottom part below the stackview, to no avail. In the end i'll use maybe something like your facebook messanger signup page type. Just wondering if it was possible somehow to get the same keyboard behavior that we get from the stackview method in the scrollview method, so basically to get the keyboard come up and push the UIelemnts up a bit if needed, rather then covering them. I'm no expert or advanced coder, maybe not intermediate even, but i enjoy finding solutiong, don't like to give up...unless maybe the solution i'm looking for its not possible.

truly was!

Setting up the bindable class, is technically another step, but the purpose is so that in your ViewModel classes, you no longer always have to set the type of the observer which is what he means by "crazy syntax". For example, you no longer have to type this -- let observer: (() -> ())? Because the bindable is setting that for you by using the `bind` initializer setting your closure that you pass in to this -- -- Inside "bind" function the type is already defined, so you just set your closure to it self.observer = observer