Search Issue Tracker
By Design
Votes
0
Found in
2020.3.35f1
2021.3.4f1
2022.1.4f1
2022.2.0a16
2023.2.0a1
Issue ID
UUM-4045
Regression
No
[Android] Player cannot be set to split-screen when "Resolution and Presentation" is set to "Windowed" and "Resizable"
How to reproduce:
1. Open the attached "case_1429380" project
2. Build and Run the "SampleScene" Scene on an Android device
3. Open the "Recent apps" window on the device
4. Tap on the built project icon
5. Observe available options
Expected result: Player can be set to split-screen
Actual result: Player cannot be set to split-screen
Reproducible with: 2019.4.39f1, 2020.3.35f1, 2021.3.4f1, 2022.1.4f1, 2022.2.0a16
Reproducible with devices:
VLNQA00458 - Google Pixel 6 (Pixel 6), CPU: Google Tensor (Whitechapel), GPU: Mali-G78, OS: 12
VLNQA00466 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
Not reproducible with devices:
VLNQA00381 - Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4, OS: 9
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00472 - Samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
Decreasing Minimum Window Width and Height solves the issue, this is expected behaviour for small screens (sw < 600dp) according to google developer guides.
From https://developer.android.com/guide/topics/large-screens/multi-window-support :
On large screens (sw >= 600dp), the platform supports all apps in multi-window mode regardless of app configuration. If resizeableActivity="false", the app is put into compatibility mode when necessary to accommodate display dimensions.
On small screens (sw < 600dp), the system checks an activity’s minWidth and minHeight to determine whether the activity can run in multi-window mode. If resizeableActivity="false", the app is prevented from running in multi‑window mode regardless of minimum width and height.