Forum Discussion
Solved
Entitlement Check failure in VRCValidator but engine reports success
Hi there, I have already attempted to reach out to submission support for this issue but was directed here for further assistance. We are in the process of uploading a finished VR build to the store...
- For anyone else experiencing this same issue, it appears the solution was that although the check was succeeding internally, the project was using C++ and hence needed the Oculus modules added to its Build.cs file. I figured this was only if you needed access to the Native C++ APIs but you'll need them no matter what if it is a code project. The build needed the following code added to the Build.cs file (LibOVRPlatform is the only addition to the public dependencies, though no sure it's necessary):
PublicDependencyModuleNames.AddRange(new string[] { "Core", "CoreUObject", "Engine", "InputCore", "LibOVRPlatform" });
Hope this helps other users with the same issue!
PrivateDependencyModuleNames.AddRange(new string[] { "OnlineSubsystem", "OnlineSubsystemOculus" });
For anyone else experiencing this same issue, it appears the solution was that although the check was succeeding internally, the project was using C++ and hence needed the Oculus modules added to its Build.cs file. I figured this was only if you needed access to the Native C++ APIs but you'll need them no matter what if it is a code project. The build needed the following code added to the Build.cs file (LibOVRPlatform is the only addition to the public dependencies, though no sure it's necessary):
PublicDependencyModuleNames.AddRange(new string[] { "Core", "CoreUObject", "Engine", "InputCore", "LibOVRPlatform" });Hope this helps other users with the same issue!
PrivateDependencyModuleNames.AddRange(new string[] { "OnlineSubsystem", "OnlineSubsystemOculus" });