Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.3.X, 2018.1.X
Votes
0
Found in
2017.3.0b3
Issue ID
958223
Regression
Yes
[Android] Animation is not playing appropriately when running the application while sharing screens
To reproduce:
1. Download and open attached "animTest.zip" project.
2. Open "test" scene.
3. Enter Play mode and notice that animation plays.
4. Build for android device which supports Miracast or any other cast.
5. Find an external android device which is capable of mirroring screens.
6. Share Your screen with a device which has project installed.
7. Mirror the screen on other device.
8. Run the application.
Expected result: Walking animation plays on both objects without interruptions.
Actual result: Animation fails to play correctly. Animation animates only the parent transform. Child objects of that parent are not animated.
Reproduced with: 2017.3.0b4, 2017.2.0f3, 2017.2.0b1
Not reproduced with: 2017.2.0a4, 2017.1.2p1, 5.6.3p4.
Regression introduced in: 2017.2.0b1.
Devices under test:
Lge LG D855 (G3)*, OS:5.0, CPU:armeabi-v7a, GPU:Adreno (TM) 330,
Build:lge/g3_global_com/g3:5.0/LRX21R.A1445306351/1445306351:user/release-keys
Sony C6603 (Xperia Z)*, OS:5.1.1, CPU:armeabi-v7a,
GPU:Adreno (TM) 320, Build:Sony/C6603/C6603:5.1.1/10.7.A.0.228/58103698:user/release-keys
Lge LG D802 (G2)*, OS:4.4.2, CPU:armeabi-v7a, GPU:Adreno (TM) 330,
Build:lge/g2_open_com/g2:4.4.2/KOT49I.D80220h/D80220h.1413914494:user/release-keys
Notes: Miracast was used to reproduce this issue. As a receiver device Sony Xperia Z4 tablet was used. Both displays fail to animate correctly. Before 2017.3 versions, second screen is fully black, but that does not prevent the animation from incorrectly animating. When screen sharing is canceled between devices everything works as expected. No repro when mirroring via AirPlay with iOS.
Fixed in: 2018.1.0b9, 2017.3.1p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment