Search Issue Tracker
By Design
Votes
1
Found in
2022.3.56f1
6000.0.36f1
6000.1.0b3
6000.2.0a1
Issue ID
UUM-96020
Regression
No
Build fails with "Error: Failed to find entry-points" when building for UWP
How to reproduce:
1. Open the attached project "bug.zip"
2. Build the project for UWP
Expected results: Build is successful
Actual results: Build fails with "Error: Failed to find entry-points"
Reproducible with: 2022.3.56f1, 6000.0.36f1, 6000.1.0b3, 6000.2.0a1
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- Gizmos are not rendered for the Base Camera when using Camera Stacking
- UI Mask Component does not apply correctly when Canvas Render Mode is set to Screen Space - Camera
- UI Toolkit Dropdown list elements use default color instead of USS color override when hovering mouse over them
- BuildOptions.Development is ignored when running a batch mode build for the win64 buildTarget
- VisionOS Player Memory Usage continuously rises when the Player has a VisionOSVideoComponent running that is set to a URL Video
Resolution Note:
The issue described here is as designed. The main problem is that the project is embedding a package named com.orangeinnov.pointcloudstreaming in the Packages folder with the root folder named PointCloudStreaming. The problem here will be that the imported managed libraries inside the package will expect to have the folder name as the package name.
For the reproduction project I managed to fix the issue by renaming the folder from Packages\PointCloudStreaming to Packages\com.orangeinnov.pointcloudstreaming.