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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
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.