We cannot even archive properly with Xcode 13 Beta 5. Complaints about compiling Combine, even though we can build and install on our physical devices. We'd love to be able to build, archive and TestFlight our changes to test support iOS 15 Beta 8.

I have not gotten it working as prior to 13.3.0 (even with picking "Simulator" from the Device Picker (rather than Mac > Simulator). It can cycle through some elements using the arrows in the Navigation section, but I cannot drill in and forget about using a mouse. I can no longer check all my accessibility for Voice Over or even for our QA Automation Engineers. Other developers are saying they are forced to go back to 13.2.1 to regain functionality.

We are experiencing the same things. Our software need to be HIPAA compliant and not allow dictation for our hospital systems. We have used this notification (textInputCurrentInputModeDidChange) and checking the primary language to prompt the user that dictation violates the hospitals policies. Now, the same code that has worked since 2014, on iOS16, it is allowing users on to bypass this security/compliance issue. It is strange that some of our search fields, the notifications fire, just not in the normal text input fields. I know that with iO16 they have some “continuous dicatiation” keeping typing and dictation active at the same time for mixed, entry. That’s probably why it no longer considers it a “change in textInputMode”) Looking for a solution. It should not be hard for apple to provide us with a notification if the button is pressed anyway.

Any updates from Apple? Or anyone? We violate HIPAA compliance by several dozen hospitals where our application is used and getting badged weekly by their compliance officers. We had no issues before iOS 16, as we could check for the keyboard using dictation and prompt the user. Apple cares about privacy - maybe they could help us out and give us an API to mitigate other company's stances on privacy.

Does anyone have a workaround for this? Apple is not responding to Feedback (bug/enhancement) filed. The solution that was suggested was to switch to a .email keyboard. While this does remove the dictation button, it is terrible for entering text as particular punctuation (like a comma or > symbol) is not there. Medical professionals use our app for secure clinician communication, and they need to be able to type a message explaining a medical condition quickly - not fumble with the keyboard layout. We are asking for 1 of the 3 options Provide a programmatic way to disable dication per app. Provide a programmatic way to set a UITextField to have .allowDication. Eg. textField.keyboardType = .default; textField.allowDictation = false Restore notification when dictationButton is pressed (via textInputCurrentInputModeDidChange) - this is what our company has used for the past 10 years