Problem with using the WFA certificate provided by Unity(or not)

Unity Engine
, ,
1

I am getting a visual studio 2019 error during a UWP build of a unity project. Depending on where I look I see the error in a couple of different textual forms. Basically it says the network password is incorrect and the WFA certificate cannot be used. I wasn’t getting this a few days ago so perhaps this isn’t a unity problem per se. Visual Studio 2019 was recently upgraded once again so I upgraded my version too but that didn’t help. Nor did turning off my firewall nor did adding turning ssdl to automatic using services.msc. I generated another WFA certificate and that didn’t change anything. Anyone know why that error might suddenly pop up? Or better yet, how to put the kibosh on that error? Thanks. I might be able to bypass the problem by shifting to non-UWP but I marginally prefer to get UWP working.

2

Can you take a screenshot of that error?

3

I’m including 2 snapshots. 1 from the build and 1 of the error window. The only other way I can think of at the moment to approach the problem is to deinstall and reinstall visual studio 2019.

8503793--1132538--Screenshot 10_10_2022 4_21_13 PM.png
8503793--1132538--Screenshot 10_10_2022 4_21_13 PM.png1920×1032 42 KB
8503793--1132541--Screenshot 10_10_2022 4_20_21 PM.png
8503793--1132541--Screenshot 10_10_2022 4_20_21 PM.png1920×1032 62.7 KB

4

You need to find “WSATestCertificate.pfx” file in your Unity project and delete it. Then, make a new build from the Unity editor.

5

Thanks for the suggestion. I think probably that was not the problem. I have got it working. I think emphasis on think is that what worked was using mmc to add the certificate to my local account on my development machine. And I also uninstalled and reinstalled visual studio many, many times. And uninstalled and reinstalled and tried to use Visual Studio 2017 too. Eventually I got it working. Notably, if you try to use vs 2017, hit the “wfa certificate bad” problem then in the error/debug text it suggests I add my certificate to my local certificate storage. Thank you very much for your suggestion however. It had not occurred to me to outright erase the old certificate and create a totally new one.

6

And before I forget, part of the reason for all the vs reinstallation activity was to make absolutely sure I was signed in to my developer account when I reinstalled a vs and NOT in my normal, “i’m just a human with a standard microsoft account” account.