-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nothing happen after click on "Add Auth Profile"? #276
Comments
I had the same issue, but it really was just opening an authentication window behind vscode that I had to find and authenticate with. |
There could be a couple things going on here. The authentication process launches a dialog (Windows) or your browser (Mac & Linux), which often launches behind the current window as @rayzorben said above. This same symptom appears when the prerequisite .NET 6.0 is not installed on the machine. If your Mac is an Apple Silicon M1/M2, you will need to install both the x64 and arm64 versions of .NET6.0 as noted in the 1.0.20 release notes. @KwernHe , if neither of those is the case, please check that running |
I had same issue. Resolved by reinstalling all dotnet-* packages and this extension... |
Since uninstalling the extension and all dotnet packages on a new Apple M1 computer did not resolve this issue for me, I'm going to document the process I used to fix my install. Though it's not likely to be something others can reproduce, it may at least help with narrowing down the problem. TL;DR First, I uninstalled the extension in an effort to "start over." Next, following steps provided here, I used this script to uninstall my previous installations of dotnet. Using this issue as a starting place, I then reinstalled both the arm64 and x64 versions of dotnet to my system. I used a terminal session to browse my dotnet installation and confirm that both versions appeared as expected. which dotnet
ls /usr/local/share/dotnet/ I then reinstalled the Power Platforms Tools extension in VS Code. At this point, I couldn't continue with that recommended solution because I still was receiving a "pac command not found" error in all terminal windows after restart (which was my original issue and the reason I was researching the Add Auth Profile problem to begin with). I browsed in terminal to the tools extension in my user library: cd ~/Library/Application\ Support/Code/User/globalStorage/microsoft-isvexptools.powerplatform-vscode/pac/tools There I eventually identified that the pac executable was not getting installed on my system. (I have no idea why!) Luckily, I had a backup from a previous system that I was able to grab the old extension install and copy it to my new system. cp -rf PATH_TO_BACKUP/Library/Application\ Support/Code/User/globalStorage/microsoft-isvexptools.powerplatform-vscode/pac ~/Library/Application\ Support/Code/User/globalStorage/microsoft-isvexptools.powerplatform-vscode/pac I then inspected my $PATH to determine which was the best location to make a symlink for the pac executable.
Finally, I restarted Code and tested everything, and I was back up and running. I successfully added an Auth Profile via Code and browser and then was once again able to execute pac commands in terminal. |
After the extension(Power Platform Tools) get installed on my VSCode, when I tried to click on "Add Auth Profile" to sign it, but nothing happens? Anyone can please help on this?
?
The text was updated successfully, but these errors were encountered: