Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment