Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
1
Found in
2017.1.0f3
Issue ID
937737
Regression
No
[Timeline][iOS] Build causes "ExecutionEngineException: Attempting to JIT compile method" in Xcode
When this project is built for iOS, `Timeline2` never plays unlike it does in the Unity Editor. Also, the following error message in Xcode is seen:
`ExecutionEngineException: Attempting to JIT compile method 'System.Linq.Enumerable:Iterate<UnityEngine.Timeline.TrackAsset, double> (System.Collections.Generic.IEnumerable`1<UnityEngine.Timeline.TrackAsset>,double,System.Func`3<UnityEngine.Timeline.TrackAsset, double, double>)' while running with --aot-only.
at System.Linq.Enumerable.Max[TrackAsset] (IEnumerable`1 source, System.Func`2 selector) [0x00000] in <filename unknown>:0
at UnityEngine.Timeline.TimelineAsset.CalculateDuration () [0x00000] in <filename unknown>:0
at UnityEngine.Timeline.TimelineAsset.get_duration () [0x00000] in <filename unknown>:0
at UnityEngine.Playables.PlayableAsset.Internal_GetPlayableAssetDuration (UnityEngine.Playables.PlayableAsset asset, IntPtr ptrToDouble) [0x00000] in <filename unknown>:0
UnityEngine.Playables.PlayableDirector:get_duration()`
Steps to reproduce:
1. Open attach project (TimelineTest.zip)
2. Build and Run for iOS device
Result: `Timeline2` never plays unlike it does in the Unity Editor. An error is seen in Xcode Console.
Reproduced with: 2017.1.0p2.
Not reproduced with: 2017.3.0a2 (linker Errors), 2017.2.0b5 (even more linker errors), 5.6 (no Timeline feature).
Tested with: iPad mini 4 iOS 10.3.2, iPod Touch 6th gen iOS10.2.1; Xcode 9.0 beta 4, Samsung Galaxy S7 Android 6.0.1.
Note: Timeline build works as expected on Android and Standalone.
Backported to: 2017.1.1p1
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