Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.1
2019.1.9f1
2019.2
2019.3
Issue ID
1167933
Regression
No
[Android][Timeline] Animated UI Object gets wrong values in Animation when its 'Z' position is set to a high value
Reproduction steps:
1. Open "WrongAnimationTargetTimeline.zip" project
2. Open "ASDF" scene and Enter Play mode
3. Press the button and notice the animation
4. Build & Run for Android
5. Press the button
6. Notice that the animation doesn't play
Expected Result: Animation plays in Android like in Editor/iOS
Actual Result: Animation doesn't play in Android
Reproduced with: 2019.3.0a11, 2019.2.0f1, 2019.1.13f1
Did not reproduce on: 2018.4.5f1, 2017.4.31f1
Reproduces with: OpenGLES2, OpenGLES3, and Vulkan; Mono and IL2CPP
Note:
Doesn't reproduce on iOS
In the Hierarchy window find "OttersOuter" GOs and change their 'Z' position to '0' to work around the issue; Reproduces if the 'Z' position is above ~+/-700
Can't repro in 2018 and below because Timeline doesn't work properly
Repro Devices:
VLNQA00272, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00109, Xiaomi MI NOTE Pro (MI NOTE Pro), Android 7.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00150, Samsung Galaxy S9 (SM-G960U), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00123, Google Pixel 2 XL (Pixel 2 XL), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00257, Sony Xperia XZ Premium (G8141), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00112, Htc M9 (HTC One M9), Android 7.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00155, Meizu PRO 7 Plus (PRO 7 Plus), Android 7.0, CPU: MediaTek Helio X30 MT6799, GPU: PowerVR Rogue GT7400 Plus
VLNQA00052, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
No Repro Devices:
Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: NOT FOUND, GPU: Adreno (TM) 308
VLNQA00255, Samsung Galaxy Note3 Neo (SM-N7505), Android 4.4.2, CPU: Exynos 5 Hexa 5260, GPU: Mali-T624
VLNQA00038, Htc Desire 510 (HTC Desire 510), Android 4.4.3, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
VLNQA00035, Motorola DROID MAXX 2 (XT1021), Android 4.4.4, CPU: NOT FOUND, GPU: Adreno (TM) 305
VLNQA00020, Samsung Galaxy S3 (SGH-T999), Android 4.3, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 225
VLNQA00061, Samsung Galaxy Nexus (Galaxy Nexus), Android 4.3, CPU: TI OMAP 4460, GPU: PowerVR SGX 540
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:
This particular case has been investigated thoroughly and as this only affects one platform and with the use of very high 'Z' position values, we have decided to not address this fix for the time being. We understand that this will cause problems for some users, and so may address this in a future version. Sorry for any inconvenience that this might cause you! A workaround would be to use lower 'Z' values for UI objects.