Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.8f1
Issue ID
1066188
Regression
No
[UWP] Vungle SDK throws an exception on IL2CPP
Steps to reproduce:
1. Download attached project
2. Switch platform to UWP
3. In toolbar select Tools -> Vungle -> Prepare Windows 10 Build
4. Build scene "MainTitleScreen"
5. Open VS solution
6. Build solution (x64, Debug, Local Machine)
Expected results: When app launches add start playing
Actual results: Exception is thrown
Reproduced with: 2018.3.0a7, 2018.2.7f1, 2018.1.9f1, 2017.4.11f1
Not reproducible on .NET backend
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] The warning "Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak" is displayed when ShaderVariantCollection.WarmUp is called
- RectangleContainsScreenPoint returns false for some points even when the points are in the rectangle
- [iOS] Stacked camera does not render when using post effects
- TextField cannot be edited in an extended Editor window when double-clicking it
- [VisionOS] visionos build do not add plugin or frameworks
Resolution Note (2018.3.X):
A couple IL2CPP bugs were fixed related to this issue, but unfortunately Vungle's Unity plugin still doesn't work on UWP Player using the IL2CPP back-end. The .NET back-end continues to function in 2018 releases.
The core reason appears to be due to the use of .NET functionality that's not currently supported in Mono's AOT profile, which IL2CPP uses. In other words, the Vungle assembly included in the plugin works with .NET but is not compatible with Mono and cannot be used with IL2CPP.
Unfortunately, there is no work-around and nothing Unity can do about this: Vungle must update their UWP plugin to work with IL2CPP.