Search Issue Tracker
Fix In Review for 2022.1.X
Votes
0
Found in
2019.4.29f1c2
Issue ID
1362681
Regression
No
[Mobile] Unity China version projects crash when Unity Analytics is disabled and IL2CPP Strip Engine Code mode is enabled
Mobile build crashes in projects created with Unity China versions when Unity Analytics is disabled and IL2CPP Strip Engine Code mode is enabled
Reproduction steps:
1. Create a new project (on Unity China versions)
2. Switch build target to Android or IOS
3. Set Scripting Backend to IL2CPP and Enable Strip Engine Code.
4. Disable Unity Analytics In Package Manager/Built-in packages.
5. Build and Run Empty Scene on Android/IOS.
Expected result: App starts normally
Actual result: App crashes
Reproducible with: 2019.4.31f1c1, 2020.3.20f1c1, 2021.1.24f1c1 (using the reproduction steps);
2019.4.31f1, 2020.3.20f1, 2021.1.26f1, 2021.2.0b15, 2022.1.0a12 (when the project is created on China versions using the reproduction steps and upgraded / downgraded to the aforementioned Global versions)
Tested with:
VLNQA00380, Xiaomi MI 8 Lite (MI 8 Lite), Android 9, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00381, Xiaomi Redmi Note 8 Pro (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
VLNQA00004, Meizu MX5 (MX5), Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
VLNQA00099, Google Pixel XL (Pixel XL), Android 10, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00052, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00358 - iPhone 12, IOS 14.1 CPU: A14 Bionic, GPU: Apple designed (Black screen; Error: Xcode)
Note: The user reported that the crash also occur on IOS. The tester's IOS device showed a black screen and an Xcode error.
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