Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
981281
Regression
No
[WSA ] Build and Run does not launch an UWP build when using VS2017 Update 4 with a password protected certificate
Steps to reproduce:
1. Create a project
2. Switch platform to Windows Store
3. Create a password protected certificate
4. Build and Run
5. Observe the exception
Expected result: Build and Run should launch an app
Actual result: Editor throws the exception
Reproduced with: 5.6.4p4, 2017.1.3f1, 2017.2.1p2, 2017.3.0f3, 2018.1.0b2
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
- 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
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2019.1.X):
If a certificate is created with a password, only a person knowing the password can use it. Visual Studio doesn't know the password, so it cannot use it. Visual studio even outputs what to do in this case:
Cannot import the key file 'WSATestCertificate.pfx'. The key file may be password protected. To correct this, try to import the certificate manually into the current user's personal certificate store.
Another workaround would be to create a certificate without a password.