Search Issue Tracker
By Design
Votes
9
Found in
4.6.2f1
Issue ID
668296
Regression
Yes
[WSA] Exception in Visual Studio (Update 5, CTP 2) using Microsoft-Ad SDK and Prime[31] plugins
Reproducible with Unity 4.6.2p1, 4.6.1f1. Visual Studio Update 5 (2013.5 CTP 2);
Repro steps:
1. open project "Microsoft Ads Plugin 2.zip";
2. build it to WSA platform;
3. open generated solution and add reference to "Microsoft Advertising SDK for Windows 8.1";
4. build and run. Press any "Display ad banner" button and observe an exception;
Exception in Visual Studio:
First-chance exception at 0x770C2F71 in Template.exe: Microsoft C++ exception: Platform::InvalidArgumentException ^ at memory location 0x059EF138. HRESULT:0x80070057 The parameter is incorrect.
WinRT information: get_left can only be called from the main thread.
Constructors and field initializers will be executed from the loading thread when loading a scene.
Don't use this function in the constructor or field initializers, instead move initialization code to the Awake or Start function.
Stack trace:
[External Code]
UnityPlayer.dll!100dc47f()
UnityPlayer.dll!1065f29a()
UnityEngineDelegates.dll!13a33f69()
[External Code]
If there is a handler for this exception, the program may be safely continued.
---
Resolution for this case is:
"Plugin bug. Plugin internally executes code on UI thread, which then calls Unity API, that can only be called from App thread."
Comments (4)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
janestap
Jun 02, 2015 09:59
Any solution for this problem?
I'm having the same issue.
Thank you.
arkon
May 10, 2015 06:21
How is this resolved? I have the same problem. What's the fix?
debuglog
May 06, 2015 19:11
Same here when using Release/Debug build, but it works in Master builds.
Majter
Mar 22, 2015 01:06
Hello :)
Is there any solution for this?
thx