Search Issue Tracker
Fixed
Fixed in 2020.3.46f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0b4, 2023.2.0a2
Votes
0
Found in
2020.3.44f1
2021.3.16f1
2022.2.2f1
2023.1.0a25
2023.2.0a1
Issue ID
UUM-25488
Regression
No
Crash on the unknown line when building a specific project
Reproduction steps:
# Open the attached project "flight simulator"
# Build And Run on an Android device
Expected result: APK is built successfully
Actual result: Editor crashes
Reproducible with: 2021.3.16f1, 2020.3.44f1, 2022.2.2f1, 2023.1.0a25
Reproducible with devices:
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Reproduced on: Windows 10 Enterprise 21H2
Notes:
- Could not get Stacktrace
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Resolution Note (fix version 2023.2.0a2):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2023.1.0b4):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2022.2.7f1):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2021.3.19f1):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.
Resolution Note (fix version 2020.3.46f1):
Disguising compute shaders as .asset files is not a supported workflow. This will cause the build to not have all required data since proper import step is missing. Compute shaders must use .compute asset type.
There is a fix incoming that will prevent the crash and spawn an error instead.