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
Comments (1)
-
IndieFist
Feb 08, 2019 17:06
We need to use Vungle with IL2CPP too.
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
- 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
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.