Getting same error, though not mentioning RealmSwift specifically (app does use it): The app references non-public selectors in Payload/IgCares.app/IgCares: authenticationDidCompleteWithError: Have not updated anything about app except making some storyboard/UI updates. Last build was accepted and approved by apple.

Suddenly having same/similar issue with new builds, today, Sept 22 2022: The app references non-public selectors in authenticationDidCompleteWithError: App has previously uploaded many versions with no issues, no new changes even remotely connected to any authentication, and in fact my app doesn't even use any such method so must be in a third-party library (RealmCocoa or Google Firebase is my guess).

Re: Edit button disappears when Add button is used, never re-appears I've verified this in my setup as well (Catalina, Xcode 12.0 beta 12A6159). If both buttons are put as "trailing", it doesn't happen. If *either* button is set as "leading", it does happen. Happens in swiftUI preview and when app is run on simulator device. I submitted it as a feedback item, but will help if others report as well. - Re: buttons initially appear as buttons in a bottom-of-screen-toolbar when not added with specific Placement parameters I see this as well, and adding specific Placement fixes the behavior to match what is shown in video. So clearly version of SwiftUI framework and Xcode shown in video are not what shipped as Beta 1 to developers.

Focusing on the crash ignores the layout constraint issue, with constraints being generated by IOS. The constraint resolution system is forced to break a constraint when this should not be happening.I'm experiencing what I think is the same root issue when working with a UITextView inside a UIStackView inside a UIScroll view, where the error messages involves ONLY constraints added by iOS:2019-12-22 09:17:24.662016-0700 IgCares[43151:3421009] [LayoutConstraints] Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it.( "<NSLayoutConstraint:0x600000b35720 'assistantHeight' TUISystemInputAssistantView:0x7fa28c5222f0.height == 44 (active)>", "<NSLayoutConstraint:0x600000b3f4d0 'assistantView.bottom' TUISystemInputAssistantView:0x7fa28c5222f0.bottom == _UIKBCompatInputView:0x7fa28c4b2980.top (active)>", "<NSLayoutConstraint:0x600000b3f480 'assistantView.top' V:|-(0)-[TUISystemInputAssistantView:0x7fa28c5222f0] (active, names: '|':UIInputSetHostView:0x7fa28e106d20 )>", "<NSLayoutConstraint:0x600000b3be80 'inputView.top' V:|-(0)-[_UIKBCompatInputView:0x7fa28c4b2980] (active, names: '|':UIInputSetHostView:0x7fa28e106d20 )>")Will attempt to recover by breaking constraint<NSLayoutConstraint:0x600000b3f4d0 'assistantView.bottom' TUISystemInputAssistantView:0x7fa28c5222f0.bottom == _UIKBCompatInputView:0x7fa28c4b2980.top (active)>