Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.53f1
6000.0.28f1
6000.1.0a5
Issue ID
UUM-87936
Regression
Yes
[Android] [iOS] Sprites used as image objects in Canvas render as rectangles in Player
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch to Android Platform
4. Build and Run
5. Observe the icons in Player
Expected result: All icons are present
Actual result: 2nd and 3rd icon is rendered as a rectangle
Reproducible with: 2022.2.0a1, 2022.3.53f1, 6000.0.28f1, 6000.1.0a5
Not reproducible with: 2021.3.45f1, 2022.1.0b1
Reproducible on:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
iOS (user reported)
Not reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- Reproducible with Vulkan and OpenGLES3
Workaround:
- Set the icon of the two assets to none, then delete the .meta of the sprite, reimport as a sprite
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas. There is a workaround by removing references and reimporting as a Sprite mentioned in the bug. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.