Search Issue Tracker
Won't Fix
Votes
15
Found in [Package]
1.2.6 - Mathematics
Issue ID
ECSB-506
Regression
Yes
[Android][ECS][IL2CPP] Player crashes when only ARMv7 is enabled
Steps to reproduce:
1. Open the attached “ECSTest” project
2. Build And Run the project on the device
Expected result: The app doesn’t crash
Actual result: The app crashes
Reproducible with: 1.0.0-exp.47 (2022.3.1f1, 2023.1.0f1, 2023.2.0a19), 1.0.11 (2022.3.1f1)
Not reproducible with: 1.0.0-exp.8, 1.0.0-exp.44 (2022.3.1f1)
Could not test with: 2021.3.27f1 (doesn’t support 1.x package version)
Testing environment: macOS Ventura 13.3.1 (Intel)
Reproducible with devices:
VLNQA00526 - Samsung Galaxy A12 (SM-A125F), CPU: Mediatek MT6765 Helio P35 (12nm), GPU: PowerVR Rogue GE8320, OS: 11
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00336 - HUAWEI Y6p (MED-LX9N), CPU: MediaTek MT6762R, GPU: PowerVR Rogue GE8320, OS: 10
VLNQA00513 - OnePlus Nord N10 5G (BE2029), CPU: Snapdragon 690 SM6350, GPU: Adreno 619, OS: 11
Not reproducible with devices:
VLNQA00498 - Google Pixel 7 (Pixel 7), CPU: Google Tensor G2, GPU: Mali-G710, OS: 13 (supports only ARM64)
Notes:
- The issue isn’t reproducible if the scripting backend is set to Mono
- The issue isn’t reproducible if the ARM64 target architecture is also checked and the device supports it
- The issue isn’t reproducible without the Entities package
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
- NavMesh Surface is baked too high above the ground, making the NavMesh Agents hover above the ground when the HeightMesh is not built
- [Android] Crash on ProcessDynamicBatchGeometryJob with OpenGL or on DrawSharedGeometryJobs with Vulkan
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
Resolution Note:
There are no fixes planned for this Bug