Closed pkbullock closed 3 years ago
I can confirm this problem and have the same issue. Just recently reinstalled my computer.
FWIW regression seems isolated to >= 1.13.0
~\spfx-1-dot-12-1> gulp trust-dev-cert
Build target: DEBUG
Found config file: serve.json
Found config file: deploy-azure-storage.json
Found config file: package-solution.json
[22:39:41] Using gulpfile ~\spfx-1-dot-12-1\gulpfile.js
[22:39:41] Starting 'trust-dev-cert'...
[22:39:41] Starting gulp
[22:39:41] Starting subtask 'configure-sp-build-rig'...
[22:39:41] [configure-sp-build-rig] Found config file: config.json
[22:39:42] Finished subtask 'configure-sp-build-rig' after 55 ms
[22:39:42] Starting subtask 'trust-cert'...
[22:39:45] [trust-cert] Attempting to trust a dev certificate. This self-signed certificate only points to localhost and will be stored in your local user profile to be used by other instances of debug-certificate-manager. If you do not consent to trust this certificate, click "NO" in the dialog.
[22:39:47] [trust-cert] Successfully trusted development certificate.
[22:39:47] [trust-cert] Successfully set certificate name.
[22:39:47] Finished subtask 'trust-cert' after 5.91 s
[22:39:47] Finished 'trust-dev-cert' after 5.98 s
[22:39:48] ==================[ Finished ]==================
[22:39:48] Suppressing - Warning - [sass] The local CSS class 'ms-Grid' is not camelCase and will not be type-safe.
[22:39:48] Project spfx-1-dot-12-1 version:0.0.1
[22:39:48] Build tools version:3.17.11
[22:39:48] Node version:v12.22.1
[22:39:48] Total duration:22 s
~\spfx-1-dot-12-1>
This seems to be a regression in our toolchain. The issue was fixed in 1.0.6 of debug-certificate-manager
, and will be picked up in the Beta drop.
As a short term mitigation, you could install a mainline version of SPFx and run the same command to install a dev certificate.
If anyone interested, here's a step-by-step to make the gulp trust-dev-cert
command work, if you've already installed the 1.13-beta.*
version (for Windows):
.npmrc
config mentioned here, otherwise you won't be able to install the 1.12.1
version of the generatornpm i -g @microsoft/generator-sharepoint
yo @microsoft/sharepoint
gulp trust-dev-cert
.npmrc
file and restore the token confignpm i -g @microsoft/generator-sharepoint
gulp serve -l --nobrowser
You should be able to see your ACE in the WebParts list.
Feel free to complete / improve / correct this procedure if something's missing 🙂
Hope that it helps.
Thanks for the write-up @michaelmaillot!
Fixed in 1.13.0-beta.11.
Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.
Versions
[Windows 10 ] Operating System [v12] Node version [4] Gulp version [@microsoft/generator-sharepoint@1.13.0-beta.5] SPFx Generator version (
npm list -g @microsoft/generator-sharepoint
)Expected or Desired Behavior
On clean machine, cannot install certificate. As per - https://docs.microsoft.com/en-us/sharepoint/dev/spfx/set-up-your-development-environment#trusting-the-self-signed-developer-certificate
Observed Behavior
CertUtil does exist:
Steps to Reproduce