Search Issue Tracker
In Progress
Under Consideration for 2022.3.X
Won't Fix in 2023.2.X
Votes
0
Found in
2022.3.22f1
2023.2.15f1
6000.0.0b12
Issue ID
UUM-67013
Regression
Yes
.framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
Reproductions steps:
1. Open the attached “UWP_Framework_Repro.zip” project
2. Switch build target to Universal Windows Platform
3. In the Project window, navigate to Assets\Plugins\iOS\ and select the Placeholder. Make sure in the Inspector window that the selected platforms are "any platform" (and no exclusion)
4. Build the project
Expected result: build succeeds
Actual result: build fails
Reproducible with: 2022.2.0a15, 2022.3.22f1, 2023.2.15f1, 6000.0.0b12
Not reproducible with: 2021.3.36f1, 2022.2.0a14
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- The workaround is to exclude "WSAPlayer" in the plugin import settings.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2023.2.X):
Closing as Won't fix due to 2023.2 reaching it's EOL.
Resolution Note:
The issue is fixed by filtering the plugin import for UWP and folder plugins .framework should not be influencing the build pipeline.