Search Issue Tracker
Fixed in 5.3.5
Votes
1
Found in
5.3.2p2
Issue ID
774295
Regression
No
[UWP] IL2CPP build incorrectly sets Output Directory and Intermediate Directory paths
When trying to publish a build or generate the App Package with enabled option "Generate app bundle" for a UWP build, the following error shows up:
Error:
_ExpandMainPriFile:
C:\Program Files (x86)\Windows Kits\10\bin\x64\MakePri.exe Dump -IndexFile C:\USER\temp_builds\cubetest_3\Win10UniCubeTest\\..\build\obj\Win10UniCubeTest\ARM\Release\split.pri -OutputFile C:\USER\temp_builds\cubetest_
3\Win10UniCubeTest\\..\build\obj\Win10UniCubeTest\ARM\Release\split.pri.xml -Verbose -Overwrite
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\AppxPackage\Microsoft.AppXPackage.Targets(1433,5): error APPX0002: Task 'ExpandPriContent' failed. Could not find a part of the path 'C:\USER\temp_builds\cubetes
t_3\Win10UniCubeTest\build\obj\Win10UniCubeTest\ARM\Release\split.pri.xml'.\r [C:\USER\temp_builds\cubetest_3\Win10UniCubeTest\Win10UniCubeTest.vcxproj]
Reproducible with 5.3.3, 5.4.0 versions.
Repro steps:
1. Build an empty project with the following settings
Platform: Windows Store
SDK: Universal 10
UWP Build Type: D3D or XAML
Scripting Backend: IL2CPP
2. Open generated project and create app package "Project->Store->Create App Packages".
Set "Generate app bundle" option to "Always", select any platform (ARM, x86 or x64), solution platform "Release" or "Master" and press create.
3. Error appears in the error list.
---
Workaround:
To fix this change the solution settings for
Output Directory and Intermediate Directory (Configuration Properties -> General -> Output Directory and Intermediate Directory.) from:
$(ProjectDir)\..\build... to
$(SolutionDir)build\bin\$(Platform)\$(Configuration)\
$(SolutionDir)build\obj\$(TargetName)\$(Platform)\$(Configuration)\
Note no slash after build. The TargetName is hardcoded as well for no reason.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
- VFX Graph font size change does not adjust Sticky Note size when smaller font size is selected
- Rendering Debugger has a “Go to Section” burger button even when the section is already opened and does nothing when pressed
- SIGSEGV error when adding EditorApplication.delayCall callback declared in complex generic type and exiting Unity in `Performanc
Add comment