The pre- and post-export methods allow you to trigger actions before and after your Unity Project is built. These methods must exist as code within your Project in the Editor folder in your Asset folder. If this folder doesn’t exist in your directory, right click within your Asset folder and go to Create__>__Folder and name it “Editor”.
Important: The UnityEngine.CloudBuild.BuildManifestObject class is only available when running in Cloud Build (as in, not locally). To compile your code locally, wrap your pre- and post-export methods in an #if UNITY_CLOUD_BUILD
block.
You set pre- and post-export methods in the Advanced Options of the build target. For more information, see Advanced Options.
Pre-export method name
To use a pre-export method, create a public static method in your Unity Project that contains the code which you want executed before the Project is exported by the Unity Editor.
public static void PreExport()
You can enable Cloud Build to pass the build manifest of the current build to the pre-export method by specifying a BuildManifestObject object as a parameter in the method signature. You can then make changes to the project or player settings before the Project is exported.
public static void PreExport(UnityEngine.CloudBuild.BuildManifestObject manifest)
When Unity Cloud Build calls the method, it passes a BuildManifestObject object as an optional parameter, where BuildManifestObject is the build manifest of the current build.
For more information, see Build manifest as ScriptableObject.
To use the post-export method, create a public static method in your Unity Project that contains the code which you want executed after the Project is exported by the Unity Editor.
public static void PostExport(string exportPath)
When Unity Cloud Build calls the method, it passes a string:
For non iOS build targets, the string contains the path to the exported Project.
For iOS Projects, the string contains the path to the exported Xcode project. You can use the path to locate the exported Xcode project to perform additional preprocessing before Xcode is called to complete the build process.
Note: If you’ve tagged any methods in your code with the Unity PostProcessBuildAttribute, those methods are executed before any methods configured as post-export methods in Unity Cloud Build.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Is something described here not working as you expect it to? It might be a Known Issue. Please check with the Issue Tracker at issuetracker.unity3d.com.
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thanks for helping to make the Unity documentation better!