Search Issue Tracker
Active
Under Consideration for 1.3.X
Votes
13
Found in [Package]
1.3.1
Issue ID
AVPB-759
Regression
No
[VisionOS] Software Keyboard appears in seemingly random locations when user activates input field
Reproduction steps:
1. Open the attached “Repro“ project
2. Build the project on “visionOS” platform (File > Build Settings > visionOS > Build)
3. Run the build on an Apple Vision Pro device or visionOS simulator
4. Select the Input Field
5. Observe where the keyboard appears
Expected result: It appears inside the user’s view in a way that is easily accessible and makes sense for the user
Actual result: The keyboard spawns below, above, or somewhere around you, but not in front of you
Reproducible with: 1.2.3, 1.3.1 (2022.3.42f1)
Couldn’t test with: 2.0.0-pre.9 (6000.0.15f1)
Reproducible on: MR on visionOS 2.0 Simulator - built using M1 Max MacOS 14.5
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
trav-h4tch
Oct 14, 2024 00:09
Any updates? This is still a big issue.
rMadrid13
Sep 26, 2024 16:56
I have performed the tests on the Apple Vision Pro device with VisionOS v2.0, the results I got in MR with Bounded Volume were satisfactory, while in Unbounded Volume they were not, the issue persists and the keyboard is not displayed in the user view, even in the v2.0.0-pre.11 (6000.0.20f1).
trav-h4tch
Sep 26, 2024 16:30
We are having this issue on device using 2.0.0-pre.9 (6000.0.15f1).
A fix is highly desired, considering our workaround is to spawn an alert asking the user to depress the bezel on the device to bring the keyboard into view.
This issue has been reported in the past by others to cause the app to fail approval by Apple.
DD_Developer
Aug 12, 2024 15:15
I see that the listed reproduction appears to only have been done in the Vision OS simulator. Please note that in our own testing we have noticed that behavior in the Simulator is different than behavior on the actual Apple Vision Pro.
Please ensure that any fix works as intended not only in the Simulator, but also on device.
Thank you!