Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.2, 2019.3
Votes
0
Found in
2017.4
2018.4
2018.4.3f1
2019.1
2019.2
2019.3
Issue ID
1172280
Regression
No
[Android] Activator.CreateInstance(Type) behaves differently with nullable types on Mono and IL2CPP
To reproduce:
1. Open attached project "NullableRepro.zip"
2. Switch to Android Platform
3. Build and run for on Android device (try IL2CPP as well as Mono builds)
4. Observe the Debug.Log output in logcat (from TestScript.cs)
Result: inconsistent nullable type values (Mono = null, IL2CPP = 0)
Reproduced in: 2017.4.0f1, 2017.4.31f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Linux] Unity licensing command on Linux pops a progress bar when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
- Frame Debugger doesn't work when using Camera.SetTargetBuffers
Add comment