Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X, 2021.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.17f1
2021.1
2021.2
2022.2
Issue ID
1367091
Regression
No
[iOS] Multi Line Mobile Input Fields show transparent background when Dark Mode is enabled and no text is in the field
Reproduction steps:
1. Set the device that this will be tested on to Dark Mode (Settings -> Display & Brightness -> Dark)
2. Open the attached project "TMPMultilineDarkThemeTest.zip"
3. Build and Run the Scene "SampleScene" on a device
4. Select any of the Input Fields in the Build
5. Delete the text present in the Input Field
Expected result: The Mobile Input Field that appears above the Keyboard remains black
Actual result: The Mobile Input Field that appears above the Keyboard becomes transparent
Reproducible with: 2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a10
Reproduced with:
iPhone 12 Mini (iOS 14.1)
iPad Air 4th Gen (iOS 14.7.1)
Could not test with:
iPhone 6 (iOS 12.4.8, Dark Mode not available)
iPhone 7 (iOS 12.3.1, Dark Mode not available)
Notes:
- Lines containing text will be black
- Single Line Input Fields are not affected by this
- The device has to be set to Dark Mode for the issue to reproduce
- Screenshots of the issue occurring show the expected black background
Comments (2)
-
Coco-Dev6
Dec 17, 2021 03:17
This fix introduced a new bug :(
-
RockSPb
Dec 14, 2021 11:27
This fix brake render if Dark Mode disabled! Lots of shader turne white.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a13
Resolution Note (fix version 2021.2):
Fixed in 2021.2.2f1
Resolution Note (fix version 2021.1):
Fixed in 2021.1.28f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.22f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.33f1