v0.10.2
11.1
4
iPhone X, iPhone X Simulator
Yes
I think I found a severe bug that can lead to an infinite loop with memory leaking like crazy, it seems I'm only able to trigger it on the new iPhone X, has anyone got his hands on the phone with the ChatExample app.
To trigger the bug:
Then your RAM goes up a lot and the app is unresponsive,
The culprit is the inputBar :
Keyboard dismisses properly.
Due to this I think we need to go with the more common solution with didMoveToWindow()
open override func didMoveToWindow() {
super.didMoveToWindow()
if #available(iOS 11.0, *) {
guard let window = window else { return }
bottomStackViewLayoutSet?.bottom?.isActive = false
bottomStackViewLayoutSet?.bottom = bottomStackView.bottomAnchor.constraintLessThanOrEqualToSystemSpacingBelow(window.safeAreaLayoutGuide.bottomAnchor, multiplier: 1)
bottomStackViewLayoutSet?.bottom?.isActive = true
}
}
I've been experimenting with a similar control in my own project. If an inputAccessoryView returns anything other than the default height for intrinsicContentSize, you get a loop. The stack trace makes it look like it's conflicting with the intrinsicContentSize of the UITextField or UITextView it contains.
Will close this as we have a PR that can fix it