iOS version 1.22.2 - Breaks support for iCade Controller

Is there an existing issue for this?

• This is a bug in RetroArch frontend
• I have searched the existing issues

Description

Hello,

Since updating Retroarch on iOS to version 1.22.2, my ion iCade controller has stopped working and is exhibiting strange behavior.
I've recreated this on two iOS devices, an iPad running iOS 12, and an iPhone running iOS 26
I've recreated this one two different iCades (because I bought another one, assuming hardware failure, but was surprised to see the same glitch!)

The glitch is strange in that the controller works initially, it can navigate the menu and even get into a game. Once in the game though, the controls only work for a few minutes, before defaulting to just holding the down direction. Afterwards the button mappings become nonsensical, and the buttons that were previously start and select try to bring up a search menu, and then bring up the DIP switch menu in the game. Restarting Retroarch starts this process over, where the controller works for a time but then glitches right out.

The new feature for update 1.22.2 lists "Native Keyboard Support" and I suspect that's breaking the iCade, as it sort of emulates a keyboard. If there's anything I can do to help track this down or test out fixes, please let me know!

Thanks,
-guyinco6nito

Expected behavior

The iCade controller works properly, as it did before Retroarch version 1.22.22

Steps to reproduce the bug

The glitch is strange in that the controller works initially, it can navigate the menu and even get into a game. Once in the game though, the controls only work for a few minutes, before defaulting to just holding the down direction. Afterwards the button mappings become nonsensical, and the buttons that were previously start and select try to bring up a search menu, and then bring up the DIP switch menu in the game. Restarting Retroarch starts this process over, where the controller works for a time but then glitches right out.

Version/Commit

1.22.2 (iOS)

Bisect Results

No response

Present in the nightly version

I don't know

Platform & operating system

iOS 26

Affected Cores

FinalBurn Neo

Environment information

I've recreated this on two iOS devices, an iPad running iOS 12, and an iPhone running iOS 26
I've recreated this one two different iCades (because I bought another one, assuming hardware failure, but was surprised to see the same glitch!)

Relevant log output

Start by reproducing the failure on iOS 1.22.2 with the iCade controller and the FinalBurn Neo core, then compare behavior before and after the Native Keyboard Support change. Done means the controller remains responsive in-game and its buttons no longer trigger keyboard, search, or DIP switch actions.