AssetDatabase.ImportPackage in Pre-Export Method

In order to include additional content in a Cloud Build that is independent of source control, we want to import a unitypackage in the Pre-Export Method. However, AssetDatabase.ImportPackage is not a blocking operation, which means the method continues execution before the package is imported. This means the Pre-Export Method is finished and the build starts before the package content is included in the project.

Is there any way to include a Unity Package in a Cloud Build at build time?

 

Thanks for the Unofficial answer. I managed to use c# reflection to call ImportPackageImmediately and it does do synchronous import, however the resulting Unity Cloud Build application does not function and the build log gives multiple warnings of type:
[Unity] Script attached to <GameObject> in scene <Prefab/Scene> is missing or no valid script is attached.
These warnings also show up when building locally using the same build script, but do not show up when building manually, so the script references are correct, they just seem to not be resolved yet when the build starts, but get resolved after.
I've tried just about every command I could find to refresh these references in the Pre-export script before building, but nothing works. This includes: AssetDatabase.Refresh (including any and all Import Flags) and AssetDatabase.ImportAsset on the entire Assets folder (recursive). Nothing seems to update the script references. They are updated correctly after the build script is finished, by the editor's own asset updating function that is always running in the background in the editor, but I don't know how to explicitly call that function inside of the build script.
For the way we want to use Unity Cloud Build, we need to be able to include unity package contents (with prefabs, with script references, etc.) in the build process.

Any help at all is greatly appreciated. Thanks in advance.

 

I've attached a very simple test case for the issue I've described above. The zip contains a project and unitypackage that can be imported and build automatically by selecting the menu item "Test/Build with UnityPackage". The resulting standalone player is corrupt and there are script reference warnings during building (as my previous post describes).

When manually importing the unitypackage and building the project, no issues occur. This suggests that the Editor does some compile/import/references resolving step that needs to be triggered by the build script (and does not happen when calling AssetDatabase.Refresh).

Once again, any help is greatly appreciated. I understand this is a slightly unorthodox use of a build script (importing a package just before building), but it greatly simplifies our (Unity Cloud Build) workflow and would be great if possible.

Thanks again in advance.

 

Thank you for the quick response. That is unfortunate, but an understandable limitation. We do unfortunately want to support iOS, so combined with other considerations, precompiled scripts are likely not the right solution. We'll have to look into an alternative, by creatively using source control probably.

Is there any chance the Unity commandline argument -importPackage <pathname> will at some point be supported by Unity Cloud Build, by supplying a web address to a unity package instead of a pathname, since a local path makes little sense with UCB?

 

Regarding the single loop and then exit issue, I seem to have figured out a way around that. I was getting the following errors after creating a project and importing a package in separate batch file steps:

Code (CSharp):

1. Compile process is not finished yet. This should not happen.
2. UnityEngine.Debug:Internal_Log(Int32, String, Object)
3. UnityEngine.Debug:LogWarning(Object)
4. UnityEditor.Scripting.Compilers.ScriptCompilerBase:GetCompilerMessages() (at C:\buildslave\unity\build\Editor\Mono\Scripting\Compilers\ScriptCompilerBase.cs:96)
5. (Filename: C:/buildslave/unity/build/Editor/Mono/Scripting/Compilers/ScriptCompilerBase.cs Line: 96)
6.  
7. Could not fetch error messages from compilerInvalidOperationException: The process must exit before getting the requested information.
8.   at System.Diagnostics.Process.get_ExitCode () [0x00000] in <filename unknown>:0
9.  
10.   at (wrapper remoting-invoke-with-check) System.Diagnostics.Process:get_ExitCode ()
11.  
12.   at UnityEditor.Utils.Program.get_ExitCode () [0x00000] in C:\buildslave\unity\build\Editor\Mono\Utils\Program.cs:104
13.  
14.   at UnityEditor.Scripting.Compilers.ScriptCompilerBase.CompilationHadFailure () [0x00000] in C:\buildslave\unity\build\Editor\Mono\Scripting\Compilers\ScriptCompilerBase.cs:105
15.  
16.   at UnityEditor.Scripting.Compilers.ScriptCompilerBase.DumpStreamOutputToLog () [0x00000] in C:\buildslave\unity\build\Editor\Mono\Scripting\Compilers\ScriptCompilerBase.cs:116
17.  
18.   at UnityEditor.Scripting.Compilers.ScriptCompilerBase.GetCompilerMessages () [0x00015] in C:\buildslave\unity\build\Editor\Mono\Scripting\Compilers\ScriptCompilerBase.cs:98
19. (Filename: C:/buildslave/unity/build/Editor/Mono/Utils/Program.cs Line: 104)
20.  

Here are the steps I was trying to do as part of my uScript package build pipeline (all of the Unity steps also have the -quit -batchmode -nographics options):

1. Unity.exe -createProject <name>
2. Unity.exe -projectPath <path from step 1> -importPackage <old package path>
3. Unity.exe -projectPath <path from step 1> [this is the step that produces the error and forces the script to stop because of a return code of 1 instead of 0]
4. copy updated files into project from step 1 [non-Unity step]
5. Unity.exe -projectPath <path from step 1> -exportPackage <directory to export> <new unitypackage path>

The errors above were happening no matter what I did in that 3rd step (i.e. when I started work on this, I did not have that step 3, so it was the -exportPackage step that was producing the error). After reading your post above about the single loop and exit paradigm, I decided to try ignoring the failure return code in step 3 and letting the script continue. The result was that I could proceed on with my build process as normal after that failure. Hope this helps someone - I was stumped on this for a while.