Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.18f1
Issue ID
UUM-27246
Regression
No
[TextMeshPro] Text stops rendering when the device orientation is changed to landscape
How to reproduce:
1. Open the attached “repro-project”
2. File → Build Settings and click Build
3. Make sure that “Auto rotate” is enabled on the device
4. Run the Player on the device
5. After the Player loads, rotate the device to landscape mode and observe the text
Expected result: The text on the cards is displayed.
Actual result: The text on the cards disappears.
Reproducible with: 2021.3.18f1
Could not test with: 2020.3.44f1, 2022.2.5f1, 2023.1.0b2, 2023.2.0a2 (Errors with custom scripts and custom packages)
Reproducible on: macOS 13.2 (Intel)
Reproducible on devices:
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 9, CPU: NOT FOUND, GPU: Adreno (TM) 630
VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00334, Xiaomi Mi A3 (Mi A3), Android 11, CPU: Snapdragon 665 SM6125, GPU: Adreno (TM) 610
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
App was not loading or just closing when testing on:
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2021.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.