Why do I see the error "No profile exists for the user"?
There are some scenarios where a user account can end up without a profile created. In IntelliJ, we attempt to detect this scenario and direct you here. In other clients, you end up with strange error messages like "User 'email@example.com' must become compliant. Compliance can be updated at..." Right now the steps to correct this problem are not simple. We hope to make this more apparent and simpler to fix in the future, but for now, here are the steps to fix this situation and create a profile:
- Open an inprivate browser (this will avoid the browser using any cached credentials that may interfere with the following steps)
- Type https://app.vssps.visualstudio.com/go/profile?mkt=en-US and in the authentication screen select 'work or school account'
- Then you will see a screen similar to this (Directory Picker):
- Select a directory from the list.
- You may be asked to create a profile, please do so.
- Repeat this process for all the directories in the directory picker (except Microsoft account) and create profiles if asked.
Everything should work after you complete these steps.
How do I get SSL/HTTPS/TLS working with Git and Android Studio?
Setting up Secure Socket Layer (HTTPS) or Transport Layer Security can be a bit tricky especially for cross platform tools like Git. There are typically several manual steps that the user has to take for everything to work properly. In this FAQ, we attempt to help you avoid common pitfalls and provide instructions to guide you on setting this up properly.
- First follow the instructions here to export the certificate. Make sure you follow the instructions carefully.
- Next verify the certificate file
- Git uses curl, so make sure curl likes the cert file by running curl against the server with the cert file in verbose mode.
On Windows "c:\Program Files\Git\mingw64\bin\curl.exe" -vvv https://server-name -cacert c:\path\to\cert\file.cer On Linux (or Mac) /usr/bin/curl -vvv https://server-name -cacert /path/to/cert/file.cer
- if you get output that contains "unable to get local issuer certificate", then curl was not able to use the certificate and you need to start over and get the right certificate. This can often be caused by NOT exporting the root certificate authority (the cert at the top of the certificate chain). If you export any other certificate in the chain it won't work with curl or git.
- if you get a 403 error, then the certificate is working. You got past the SSL handshake and it actually tried to connect to the server. The 403 is returned because there were no credentials.
- If curl is successful,
- Finish the steps in the blog on how to install the cert in the git cert store.
- Then try git directly by attempting to clone the repository
git clone https://server-name/path/to/repo
- You should be prompted for credentials by git. If you get an error, make sure your credentials are correct.
- If git clone worked, then try Android Studio
- Open Android Studio and "Checkout from Version Control" -> "Team Services Git".
- If you see any errors, save the console output in the Version Control window as well as the logs for further investigation.