Search Issue Tracker
Fixed
Fixed in 2022.3.29f1, 6000.0.2f1
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
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
Resolution Note (fix version 6000.0.2f1):
The issue is fixed by filtering the plugins for UWP for folder plugins like .framework or .plugin and now should not be added to the build process.
Resolution Note (fix version 2022.3.29f1):
The issue is fixed by filtering the plugins for UWP for folder plugins like .framework or .plugin and now should not be added to the build process.