*Steps to reproduce:*
# Open the attached "WebCamTexture-TestProject.zip" project  
# Switch to Android Platform in File > Build Settings
# Make sure that all Scenes are added in the Scenes in Build
# Go to Edit > Project Settings > Player > Other Settings
# Select GameActivity as an Application Entry Point
# Build and Run the application on a device
# In the application open "03_ Set FPS_Test"
# Enter FPS into the Input field "Enter target FPS"

*Expected:* There is a button that lets to confirm input
*Actual:* The button that lets to confirm input is missing (replaced with new line button), it's impossible to set target FPS. Reproducible with all keyboard types (Numerical, Default, ASCII capable etc.)

*Reproducible with:* 2023.1.0b8, 2023.2.0a6
*Could not test with:* 2020.3.46f1, 2021.3.21f1, 2022.2.11f1 (GameActivity is not supported)

*Reproduced with devices:*
* VLNQA00467 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 12
* VLNQA00460 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 13
* VLNQA00230 - OnePlus 6T (ONEPLUS A6013), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 9.0.0
* VLNQA00323 - Galaxy Note 10 USA (SM-N970U), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 11
* VLNQA00090 - Samsung Galaxy S8 (USA) (SM-G950U), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 7.0.0
* VLNQA00500 - Google Pixel 7 CPU: Google Tensor G2. GPU: Mali-G710, OS: 13

*Notes:* 
* Everything works as expected if the Application Entry Point is set to Activity
* *{color:#de350b}Once fixed reenable TestManualKeyboardInteractions::ValidateEnterKeyInteraction test for GameActivity in Tests\EditModeAndPlayModeTests\TouchScreenKeyboard\Assets\Tests\TestManualKeyboardInteractions.cs{color}*