Post not yet marked as solved
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
Post not yet marked as solved
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.
Post not yet marked as solved
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.
Post not yet marked as solved
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.
Post not yet marked as solved
Same issue. I have been working with support and sending them screenshots of AppStoreConnect.
I was able to upload a bug fix release (point release), but I cannot create the new version itself.
The other day, I could not see any of my Apps in the App tab. That problem turned out to be using some Safari extensions.
This new issue of not being able to create a new app version is experienced in both Safari and Chrome.
Post not yet marked as solved
I've had multiple problems with the What To Test portion of TestFlight over the past month. Mine would constantly give me "invalid characters" message, and then fail to save. I filed multiple Feedback bugs and Apple did respond that they were unable to produce. I sent them the text file of the text I am pasting in and have not heard back.I had NO HTML or special characters. My only solution was to paste my text and remove paragraph by paragraph until I found the offending sentence. There was nothing special in the sentence, something rewording it allowed me to save - other times, I just had to cut the sentence out. It was frustrating. Happened on 3 different builts in August with different release notes.
Follow-up.I was able to work around by using Xcode 10, adding the model mapping file through the wizard as normal, then re-open in Xcode 11 beta. All worked.
