Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.1.X, 2017.2.X, 2017.3.X, 2018.1.X
Votes
19
Found in
2017.1.1f1
Issue ID
954427
Regression
No
[Android] Crash on builds with .NET 4.6 scripting runtime selected when null reference exception appears
To reproduce:
1. Download and open attached "Android_Net46_Bug.zip" project.
2. Build and run for android device.
Expected result: Application loads up correctly, without crashing.
Actual result: Application crashes instantly after it's loaded.
Reproduced with: 2017.3.0b2, 2017.2.0f2, 2017.1.1p3, 2017.1.0a6
Not reproduced on: 2017.1.0a5 - new .NET4.6 not present
Devices under test:
Reproduced with:
Lge LG H815 (G4), OS:6.0, CPU:arm64-v8a, GPU:Adreno (TM) 418,
Build:lge/p1_global_com/p1:6.0/MRA58K/1620215065b6f:user/release-keys
Samsung SM G800F (Galaxy S5 Mini), OS:6.0.1, CPU:armeabi-v7a, GPU:Mali-400 MP, Build:samsung/kminiltexx/kminilte:6.0.1/MMB29K/G800FXXU1CQA1:user/release-keys
Google Pixel, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 530,
Build:google/sailfish/sailfish:8.0.0/OPR3.170623.007/4286350:user/release-keys
Not reproduced with:
HUAWEI EVA L19, OS:7.0, CPU:arm64-v8a, GPU:Mali-T880,
Build:HUAWEI/EVA-L19/HWEVA:7.0/HUAWEIEVA-L19/C432B386:user/release-keys
iPad Mini 3 (iOS 10.3.2)
Notes: Calling "throw new NullReferenceException()" does not trigger the crash. If Scripting runtime version is set to Stable( .Net 3.5 Equivalent), everything works as expected. Does not happen when Scripting backend is set to IL2CPP.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Dragging any draggable query block makes the query block background invisible until hovering on it again
- Alternating row background lines in table view are left over when clearing the search field
- Getting duplicate search query results for created scripts in search window
- There is no information or any visual indicator/response when some properties are set as inline value in the UI Builder
- Dialog Text during the Confirmation stage of Bug Report Submission is cut off when the Bug Reporter Window is resized to it's smallest possible size
Add comment