if you created a 2D project, create a new 2D project and copy that manifest. Is there any way of forcing Cloud Builds to re-generate the AndroidManifest.xml file ? Clean Builds don't do the trick. If this has happened to you, the solution is super easy, just create a new project the exact same way as the last one, and copy the manifest from the new one onto the old one. I actually had the same issue in local builds, and had to manually delete Temp/StagingArea/AndroidManifest.xml in order for my new changes to manifest to be applied in my local builds as well. It's building right now, we'll see if this works. IN PROGRESS: I have a preprocess script that will attempt to delete Manifest in Temp/StagingArea before the build, but I don't believe it will be able to find and delete it (says file doesn't exist in local builds, even though it does). I can't find a way to force Cloud Build re-generate a new manifest
Unity Cloud Build is using a previously cached manifest, like it does in Temp/StagingArea (as any changes I do aren't reflected, like adding new permissions etc) I have deleted all AndroidManifests.xml in the project, same result
I have deleted all plugins and no longer have a Plugins folder Place a single folder in the folder buffer (option + up) then use the Unity Git Submodule Adder action (option + right arrow). using the unitysubmoduleadder keyword which will then provide a folder filter for you to choose your Unity project.
UNITY CLOUD BUILD SUBMODULES FOLDER CODE
No code is calling WebCamDevices in the projectīuilding from the local editor results in a manifest with no permissions (all good!)īuilding from Cloud Builds results in the exact same manifest as before (all previous permissions)ĭoing a Clean Build still uses that older manifest, and does not solve the problem Usage is simple and works in two different ways: 1. Now, I need a version without this camera permission.Ĭhanged manifest to remove all permissions that I wish to remove My previous builds had a manifest with Camera permission (intended). I've checked many posts about fixing the manifest in Cloud Build, but these attempts are unsuccessful as it looks like it's a different issue.
0 kommentar(er)
