Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0f3
Issue ID
958817
Regression
Yes
[WSA] Can not build and run after upgrading a project from 2017.1
Steps to reproduce:
1. Create a project with 2017.1
2. Switch platform to Windows Store
3. Create a Cube
4. Build and Run (You should be able to Build and Run)
5. Switch platform to Standalone and close Unity
6. Open the project with 2017.2/2017.3/2018.1
7. Switch platform to Windows Store
8. Build and Run
9. Observe the errors
Actual result: The errors are thrown
Expected result: You should be able to Build and Run a project
Reproduced with: 2017.1.2p2 -> 2017.2.0p1, 2017.1.2p2 -> 2017.3.0b7 , 2017.1.2p2 - >2018.1.0a2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
Add comment