Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.1.5f1
Issue ID
1052940
Regression
No
[UWP] [IL2CPP] PInvoke triggers an exception when building Vuforia project
Steps to reproduce:
1. Create new project
2. Add VuMark in the scene
3. Select import assets when the pop up show up
4. In Player setting under XR tab enable Vuforia
5. In Player settings under Publishing tab enable InternetClient WebCam and Microphone
6. Switch platform to UWP and Build VS2017 solution
7. Open VS2017 solution
8. Build solution (Debug x64 Local Machine)
Expected results: Project is successfully build
Actual results: Exception is triggered
Exception thrown at 0x00007FFB42EBA388 in New Unity Project (4).exe: Microsoft C++ exception: Platform::AccessDeniedException ^ at memory location 0x000000FE9B1FE020. HRESULT:0x80070005 Access is denied.
WinRT information: Access is denied.
Reproduced with: 2018.3.0a3, 2018.2.b10, 2018.1.7f1, 2017.4.6f1
Tested with: Vuforia 7.1.35
-
Industry4O
Jan 16, 2019 15:54
Solved this by openning Package.appxmanifest in Visualstudio (after Build the project in Unity) and enable InternetClient WebCam and Microphone there again before compiling.
-
Industry4O
Jan 16, 2019 15:54
Solved this by openning Package.appxmanifest in Visualstudio (after Build the project in Unity) and enable InternetClient WebCam and Microphone there again before compiling.
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
- Double separation lines are present in a kebab dropdown menu
- [URP] CommandBuffer: built-in render texture type 3 not found while executing warning is thrown when Game view is open and OpenGL is used
- User gets "Sorry...that page seems to be missing" when click a help icon
- Horizontal Scrollbar appears in the Inspector Window when the Volume Component is added
- Build Profiles - Feature Request: Editor restart button would improve the user experience
Resolution Note (2018.3.X):
[various]
XR Management has evaluated this issue and determined that it does not meet our current bug severity threshold. If you would like your issue to be reviewed again, please re-submit your bug.