Hi
Since Unity 2018.3.x UI Mask doesn’t work on Android 5.0.1.It doesn’t draw itself and its children.
Tested on Samsung Galaxy S4 GT-I9500 Android 5.0.1
On Unity 2018.2.x and older everything’s ok with mask. It has the issue only on Unity 2018.3.x and with Android 5
How can reproduce the issue.
Just create a new project in Unity 2018.3.x (we used 2018.3.6 and 2018.3.7)
Switch target on Android
In the new empty scene create Canvas, then create UI Mask into the Canvas.
Create UI Image as a child object of Mask. Any combinations.
Build the project for Android and test on Android version 5
Could you please submit a bug-report as described in this document:
It’s important that you report these issues together with a reproduction project if you want them to get fixed. If you don’t do it, it might be a long time until someone else reports them or until Unity Technologies find them.
After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. You can post this Case number here (in this forum thread) for Unity staff to pick up, in case they see it.
Same issue here since upgrading a project from 2018.2 to 2018.3. We experience a few Android devices not drawing scrollview content and other Mask clipped content anymore. OS version 4.4.2 - 5.x (not sure about newer versions). Looks like OpenGLES2 affected only, x86 and arm.
Removing the mask component makes the scrollview render correctly on this affected devices
That’s a major bug, and very hard to find the causing issue, or a term to search (simply my whole UI wouldnt draw with no log messages, I didnt know where to look, found this by luck), that’s why this thread is not flooded with complains.
Please Unity team prioritize this issue, it seems it is being ignored by you guys (20+ days since this thread started and it’s a major bug!). I cant update my game in production due to this bug. If I knew about this bug last week I would annoy you guys at GDC to get this fixed.
Yes, also rather major for us. We restructure our project to make use of nested prefabs, so can’t go back to 2018.2 and have a lot of users complaining with no chance to fix this by ourself…