iOS 26 beta: UIResponder inputAccessoryView no longer integrates seamlessly with system keyboard

Question

Created 1w

Replies 2

Boosts 3

Participants 2

Prior to iOS 26, it was possible to design an inputAccessoryView(Controller) that would integrate seamlessly with the system keyboard, by which I mean appearing as a natural extension of the system keyboard. For example, using CYRKeyboardButton <https://github.com/tmcintos/CYRKeyboardButton>.

To date, I have successfully used this to provide an enhanced numeric key row within my apps, which is a distinguishing feature of these apps. It took a lot of engineering and testing effort to perfect this design. However, with iOS 26 the design is completely broken due to the system keyboard UI change, which makes it impossible to display an inputAccessoryView seamlessly along the top of the system keyboard (see attached screenshots).

In my opinion, it is just plain reckless for Apple to make these kinds of trivial UI changes, which break existing app designs without adding any significant value to the user experience.

iOS ≤ 18.x:

Screenshot 2025-06-11 at 2.04.20 PM.png

iOS 26 beta:

Screenshot 2025-06-11 at 2.04.48 PM.png

Boost

Answer 1

DTS Engineer OP

Apple

1w

The best way to provide feedback on the new UI design is to file a feedback report. If you haven't yet, I'd suggest that you do so and share your report ID here for folks to track. Thanks.

Best,
——
Ziqiao Chen
 Worldwide Developer Relations.

1

Answer 2

tkmcintosh OP

6d

Submited FB17978212 (iOS 26 beta: UIResponder inputAccessoryView no longer integrates seamlessly with system keyboard):

Prior to iOS 26, it was possible to design an inputAccessoryView(Controller) that would integrate seamlessly with the system keyboard, by which I mean appearing as a natural extension of the system keyboard. For example, using CYRKeyboardButton <https://github.com/tmcintos/CYRKeyboardButton>.

To date, I have successfully used this to provide an enhanced numeric key row within my apps, which is a distinguishing feature of these apps. It took a lot of engineering and testing effort to perfect this design.

However, with iOS 26 the design is completely broken due to the system keyboard UI change, which places a margin with edge and rounded corners above the top row of the system keyboard. This makes it impossible to display an inputAccessoryView seamlessly along the top of the system keyboard (see attached screenshots showing previous and current app behavior after rebuilding with Xcode 26 and running on iOS 26 with no modifications to this functionality).

This sort of UI change feels reckless—breaking existing app designs without adding any significant value to the user experience—and forces developers to waste time on rewriting their debugged, stable apps, likely creating more bugs instead of focusing on delivering the bug fixes and enhancements that they had planned.

1