iOS17 UITextView inputView becomFirstResponder does not work

UIView *cv = [[UIView alloc] initWithFrame:CGRectMake(0, 0, _customKBView.frame.size.width, _customKBView.frame.size.height)]; cv.backgroundColor = [UIColor blueColor]; [cv addSubview:_customKBView];

_fakeTxtView.inputView = cv; [_fakeTxtView becomeFirstResponder];

We have the same issue. Looping of [RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID

I have the same issue.

I am not sure if it's what's causing of my screens that has couple of textFields to jump down the screen...

Same here. Also getting issues that inputAccessoryView is not showing correctly for iOS 17

I have the same situation

I had the log message in the iPhone simulator running iOS 17 until I upgraded to Ventura 13.5 (22G74) just now, still using XCode Version 14.3.1 (14E300c). My custom keyboard (in-app; not system wide keyboard) was is behaving erratically (disappearing, after a few taps in the app, and the message~~

-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID

would appears in the logs).

Now, after the upgrade (Ventura 13.5 (22G74) just now, still using XCode Version 14.3.1), I've been trying to replicate the problem, but so far it does not occur anymore...

I take it back: it's indeterministic: a few recompiles later the issue is still here.

same issue and I'm on Xcode 15 beta 7. ****. Hope they fix this.

-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID

update ios 17 beta 8 is ok

Beta 8 same issue here!

Same issue here... I really hope they will find a solution otherwise the banking app where I'm working on will have some serious problems... The textfiled does not become firstResponder.

I noticed UITextFields don't always deinit when closing its VC (or using removeFromSuperview()), but only if it has become first responder at least once.

Actually, if you have a VC with multiple UITextFields, let one become first responder, then close the VC, ALL UITextFields won't deinit! Then if you activate another UITextField in another VC they will deinit after all. I believe it happens more often when textContentType isn't nil.

To check yourself just subclass UITextField and check the deinit calls in the console:

class TestTextField: UITextField {   
    deinit {
        print("deinitted textfield \(self.placeholder ?? "") \(self.text ?? "")")
    }
}

I am also getting this issue after the update that came with he release of iOS17, Has anyone had success in the search for the cause?

The warning seen in the console occurs the exacty mooment I click insite of the TextField that you can see in the Image on the right.

Typing in the text field continues to through addition warnings although different to the original.

Same issue for me

Same issue here with iOS 17.

I try to work with .searchable modifier, the first tap is laggy, and after that, every tap will trigger de warning :

-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID

+1

-[RTIInputSystemClient remoteTextInputSessionWithID:performInputOperation:] perform input operation requires a valid sessionID