Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
0
Found in
2019.3.0a5
2019.3.1f1
2019.4
2020.1
2020.2
Issue ID
1222808
Regression
Yes
[Mobile] Build succeeds but IL2CPP error "Unhandled Exception: System.Collections.Generic.KeyNotFoundException:" is thrown
How to reproduce:
1. Open the attached ElasticSearchIL2CPPError.zip project
2. Build for iOS/Android
Expected: Build succeeds without errors
Actual: Build succeeds but IL2CPP errors are thrown
Reproducible with: 2019.3.0a5, 2019.3.16f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a16
Not reproducible with: 2018.4.24f1, 2019.2.21f1, 2019.3.0a4
Note:
- The project uses a third-party .dll
- Error: Unhandled Exception: System.Collections.Generic.KeyNotFoundException: The given key 'System.Collections.Generic.IEnumerator`1<!0>
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
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0a6
UnityLinker : Fix a case where an interface could be incorrectly removed from a type when no .ctor for that type was marked.
Resolution Note (fix version 2020.2):
UnityLinker : Fix a case where an interface could be incorrectly removed from a type when no .ctor for that type was marked.
Fixed in: 2020.2.0f1
Resolution Note (fix version 2019.4):
UnityLinker : Fix a case where an interface could be incorrectly removed from a type when no .ctor for that type was marked.
Fixed in 2019.4.17f1