[BDS-5167] Can't close virtual keyboard on Minecraft for Amazon Fire TV Created: 08/May/20  Updated: 09/May/20  Resolved: 09/May/20

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.14.60
Fix Version/s: None

Type: Bug
Reporter: Brian Vogt Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None

Confirmation Status: Unconfirmed

 Description   

I am trying to help my son with Minecraft on the Amazon Fire TV. I have a Fire TV 2.  One critical problem that arises whenever he plays is when he chooses to go into chat/command mode on the game, the virtual keyboard pops up. We do have a bluetooth keyboard so that's not necessary. The problem is that there doesn't seem to be any way to close the virtual keyboard. The buttons on the remote (e.g. the back button) don't do anything. I press the arrow key (similar to an enter key) or the back key on the virtual keyboard but nothing happens. The buttons on the game controller operate the game that is in the background behind the keyboard. Nothing I do will close the virtual keyboard and I have to quit the game by pressing the home button on the remote. This makes the game unusable.  



 Comments   
Comment by [Mod] bemoty [ 09/May/20 ]

Thank you for your report!
However, this issue is Invalid.

This is related to a different project. Use one of the links below to go to the correct project.
Minecraft: Java Edition — Windows, Mac, and Linux
Minecraft Launcher — Bugs about the Minecraft Launcher specifically
Minecraft: Bedrock Edition — Gear VR, iOS, Android, Windows 10 (from the Windows store), Xbox One, Windows 10 Mobile, Fire TV, Nintendo Switch, and PS4
Minecraft Earth — AR Compatible Devices
Minecraft Dungeons — Action-adventure title set in the Minecraft universe

Please don't forget to search for an existing issue matching yours in the appropriate project before raising a new one.

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Customer Support – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs

Generated at Sat Jan 11 07:32:01 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.