Skip to main content
ImmergenceStudio01
Inspiring
August 17, 2026
Solved

Keyboard Overlay No Longer Appears After the v2.7 Update

  • August 17, 2026
  • 18 replies
  • 746 views

Hello,

We have encountered an issue with the keyboard overlay since updating to version 2.7.

Our application is published on the Meta Horizon Store.

The exact same application build works correctly on another headset that is still running version 2.6: when the user selects an input field, the keyboard overlay appears normally.

However, on the headset updated to version 2.7, the keyboard overlay no longer appears, so users cannot enter text.

Has anyone else experienced this issue since the update?

Meta team, could you please confirm whether this is a known bug introduced in version 2.7 and keep us informed about a possible fix or workaround?

Thank you.

      Best answer by ImmergenceStudio01

      I am not alone ! Ok Wang_shi !

      So i found a solution for Keyboard overlay with 2.7 ! Use Unity Version 6000.3.1f1 and it works by magic. It is unity problem i think

      18 replies

      ImmergenceStudio01Author
      Inspiring
      August 17, 2026

      ADB Logcat say : 

      Timeout while waiting for keyboard to become visible

        WangShi
        WangShi
        Participant
        August 18, 2026

        I’m also a developer. Many users have reported this issue, and I hope the official team can fix it as soon as possible.

        ImmergenceStudio01AuthorAnswer
        Inspiring
        August 18, 2026

        I am not alone ! Ok Wang_shi !

        So i found a solution for Keyboard overlay with 2.7 ! Use Unity Version 6000.3.1f1 and it works by magic. It is unity problem i think

          WangShi
          WangShi
          Participant
          August 19, 2026

          Awesome, I’ll go test it out.

          berkc1489443
          Participant
          August 25, 2026

          We are also experiencing same issue. One of our headsets were not updated to 2.7 yet and it was working yesterday. This morning, it decided to update itself then the keyboard stopped showing up, and I saw this topic here. Also, the app we published in the store also does not have keyboard working which was built a month ago with no change on it. 

          Is there any update on this?

          Unity version: 6000.5.9f1
          Meta All-in-One SDK version: 205.0.0

          ImmergenceStudio01Author
          Inspiring
          August 25, 2026

          Unfortunately, we do not have any further information about the status of this issue. It appears to be something Unity and Meta need to resolve together.

          We experienced exactly the same problem: an application that had already been published and was working correctly stopped displaying the virtual keyboard after the headset updated to v2.7.

          For now, the only workaround we have found is to rebuild the application using Unity 6000.3.1f1. We tested several Unity versions, and this is the only one where the keyboard still appears correctly with the current v2.7 update.

          You can keep Meta All-in-One SDK 205.0.0, as it works correctly with this Unity version.

            Maccyb123
            Honored Contributor
            August 25, 2026

            I don't use the keyboard overlay but just tried it after getting v2.7 and then yesterday another build number update. It's working on mine,, I wonder did the new build number fix it as I never tried it after the initial version. Maybe a fix is going out?? 

              asquaredevs
              asquaredevs
              Participant
              August 25, 2026

              We also came across this issue last Friday when all of our headsets updated and the keyboard stopped working. We rolled back from 6.4 to 6.3 as mentioned above and this does work. 

              I'd also like to ask that we not mark this as the solution for the problem, as that marks the forum post as resolved and is probably unlikely to be addressed. Also, if it wasn't reported to Unity it won't be addressed. I'll go ahead and submit a bug for that either way.

                berkc1489443
                Participant
                August 25, 2026

                For more details, the log we saw when interacted with an input field:

                Hiding input field is not supported when using GameActivity./nTMPro.TMP_InputField:ActivateInputFieldInternal()
                TMPro.TMP_InputField:LateUpdate()

                Rollbacking to 6.3.22f1 did not resolve the problem immediately. But, 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">

                Resolved the issue for us. Now, we are able to interact with the input fields. However, this is just a workaround, and we don't want to use v6.3. I hope Meta sees the topic and fix this issue soon. Thanks for sharing the details. 

                I just saw your meesage Maccyb123​ . Our devices have the same build number which is 5243367.3220.520. I am not sure if this is the latest one or they are already working on it. But thanks for the information.

                berkc1489443
                Participant
                August 25, 2026

                For more details, the log we saw when interacted with an input field:

                Hiding input field is not supported when using GameActivity./nTMPro.TMP_InputField:ActivateInputFieldInternal()
                TMPro.TMP_InputField:LateUpdate()

                Rollbacking to 6.3.22f1 did not resolve the problem immediately. But, 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">

                Resolved the issue for us. Now, we are able to interact with the input fields. However, this is just a workaround, and we don't want to use v6.3. I hope Meta sees the topic and fix this issue soon. Thanks for sharing the details. 

                I just saw your meesage Maccyb123​ ​ . Our devices have the same build number which is 5243367.3220.520. I am not sure if this is the latest one or they are already working on it. But thanks for the information.

                  asquaredevs
                  asquaredevs
                  Participant
                  August 25, 2026

                  I did also see that changing GameActivity to Activity could fix the issue - if the editor allows for that change. We specifically used 6000.3.1f1. Between that version and 6000.3.22f1 there may have been a change that prevented the need of having to update the manifest ourselves.

                  MrFlavio97
                  MrFlavio97
                  New Participant
                  August 31, 2026

                  Same problem with the latest Unity version. The problem IS NOT solved!

                  asquaredevs
                  asquaredevs
                  Participant
                  September 1, 2026

                  Unity has updated my bug report to In Review. Will post updates when I see them.

                    asquaredevs
                    asquaredevs
                    Participant
                    September 10, 2026

                    By the way, wanted to update here for everyone - response from Unity:

                    Thank you for bringing this issue to our attention!

                    We are aware of this issue, and it is already being worked on. Sadly, we cannot provide an issue tracker link since this bug will only be tracked internally.

                    We highly appreciate your contribution. If you have further questions, don't hesitate to ask

                    Thanks,

                    Robertas

                    Customer QA Team

                      berkc1489443
                      Participant
                      October 1, 2026

                      Hello all,

                      We just updated to Meta SDK v207, Horizon OS v208 5243367.4880.520, Unity 6.6.4f1. Keyboard issue still exists. We can not interact with the inputfield. I am curious in which version they are going to bring a fix. Should we create our own keyboard like old days? Anyone from Meta team, is there any ETA? Or does anyone else have a chance to test any other workaround other than downgrading Unity 3 versions?

                      Terms & ConditionsAccessibility statement