Skip to main content
binariidev
New Participant
September 4, 2026
Question

Update 2.7 causes input fields to fail in Unity App

  • September 4, 2026
  • 7 replies
  • 259 views

Yesterday my Meta Quest 3 updated from version 2.6 to 2.7. According to patch notes, this update is still in the PTC and my device is not in it, so I don't know if there's other issues also there.

Launching an Unity App that worked well in version 2.6, in 2.7 the inputs fields fail to show the System Keyboard. Immersive debugger only shows one warning in the first attempt at interacting with one:

hiding input field is not supported when using game activity

Interacting with the input fields also makes the program freeze for a bit.

Trying to make the keyboard appear with code or even changing the TMP_InputField code doesn't work either. Has anyone had the same issue? Any workarounds you can think of? Also, could this be related to this other discussion?

 

Edit: Unity version is 6.3 LTS and I'm using the latest version of Meta SDK. All UI and input related packages are also up to date

    7 replies

    binariidevAuthor
    New Participant
    September 4, 2026

    I have checked if a factory reset fixes the issue. It isn't the case, so this is something different.

    pocce90
    New Participant
    September 14, 2026

    Hi, we are experiencing the exact same issue on our end. Our Unity app was working perfectly on v2.6, but after the Quest 3 updated to v2.7, the system keyboard fails to show up for input fields. We are also seeing the same brief freeze and the 'game activity' warning in the logs. We're on Unity 6.3 LTS with the latest Meta SDK as well. We haven't found a workaround yet

      binariidevAuthor
      New Participant
      September 16, 2026

      I've been trying to contact support for help with this issue, but  the dumb AI model that they use doesn't say anything useful. I guess we'll have to wait for an update because the forum seems pretty dead as well...

      steve40
      steve40
      Honored Contributor
      September 16, 2026

      Meta Horizon Developers Feedback Center

        binariidevAuthor
        New Participant
        September 16, 2026

        I don't know why I couldn't find that page. Thanks for the help! I'll see if I can find a solution there

          qingqiu2025
          New Participant
          September 28, 2026

          Use Unity Version 6000.3.1f1
          or

          changing the Player Settings/Other Settings/Application Entry Point to Activitiy (which is still available in v6.3) and updating the manifest activity:

          <activity android:theme="@android:style/Theme.Black.NoTitleBar.Fullscreen" android:configChanges="locale|fontScale|keyboard|keyboardHidden|mcc|mnc|navigation|orientation|screenLayout|screenSize|smallestScreenSize|touchscreen|uiMode" android:launchMode="singleTask" android:name="com.unity3d.player.UnityPlayerActivity" android:excludeFromRecents="true" android:exported="true">

           

          jernejpremru
          New Participant
          October 12, 2026

          Our app has user logins, pins etc relying on system keyboards and ofc this issue pops up when we give a client a headset with the demo application to show at a meeting. Long story short they couldn’t use the app, we look like we cant make an app with an input field, we had to patch things in a day AND probably lost a client. really fkd up that they roll out updates like these without testing all the stuff first. In the real world people can get fired because they get blamed for stuff like this not working. It really shows sadly that Meta doesnt have any “real” competition and they can afford to put stuff like this out. 

          Terms & ConditionsAccessibility statement