Closed HarrisonHough closed 4 months ago
Overally looks good, but do we want this to be disabled by default? Or should we still add the macro to the unity, when project is imported? we don't know how many people don't need the permissions and how many do right?
It's a good question. Generally I would say that people would only need the permissions if targeting mobile AND they don't want to use the CAC. If they are targeting VR however (which includes mobile/android) then permissions need to be removed if they plan to release to the quest store. If we still wanted it enabled by default we can either:
The main problem I have with having permissions enabled by default is that it's forcing things that may not be need that can cause bugs, and could be overriding some of their own build post processors. However on the flipside if they do actually need the permissions for their app then of course being enabled by default would be useful
SDK-697
Description
RPM_WEBVIEW_PERMISIONS
With this update it will be disabled by default but they can re-enable by adding the above define symbol into player settings. This will help developers when submitting to marketplaces that don't allow camera or other specific permissions.Changes
Added
Updated
Removed
How to Test
Checklist