Solution 3:
The above method didn’t work, so I killed gradle and Gradle in the project directory, created a new project, copied the two folders in the new project, and the Studio returned to normal.

In addition to the above methods, based on personal experience can also be:
This can also happen if a project developed on an original device is about to be moved to another device (the gradle update download is very slow)
At this point, first go to the Settings of Android Studio under the new device and turn off the Proxy

Then go to the directory of Gradle

Use the.gradle directory for the original device instead of the gradle directory for the new device.

Solutions:

using the configuration file, put the information such as password in a configuration file, run the package when read from the configuration file (the configuration file is best stored in a safe place) to replace the ProtectionLevel that package EncryptSensitiveWithPassword and set the password, open CommandLines after deployment, will be prompted for a password, after input, run the package successfully. After deployment, enter DataSource, check the required DataSource, and then enter CommandLines. The previously selected DataSource will be automatically generated in it, and Password will be edited into it.

The first is a formal approach, good security, but more troublesome, because to deploy to a remote server, but do not have the authority to put configuration files into this server, so temporarily unable to adopt this approach.
The latter two are gradually tried out by myself. They are simple and not safe (especially the third one).

Reproduced in: https://www.cnblogs.com/Muller/archive/2012/02/16/2354377.html

Git pushed “Fatal: Authentication failed”
Question why
You set up two-step validation earlier

 If you enabled two-factor authentication in your Github account you won't be able to push via HTTPS using your accounts password. Instead you need to generate a personal access token. This can be done in the application settings of your Github account. Using this token as your password should allow you to push to your remote repository via HTTPS. Use your username as usual.

The solution
Update the branch

git remote -v 
git remote remove origin 
git remote add origin [email protected]:user/repo.git  

## Resources
[1].Git push results in “Authentication Failed”

Reproduced in: https://www.cnblogs.com/OneFri/p/11123584.html

CreateProcess Error =267 directory name invalid

After searching on Bing for a long time, I couldn’t find a corresponding solution, so I asked for help from my predecessors.
The elder say: you see, somebody said the directory name is invalid, so you just change the directory (project) name.
There is an & AMP in the project name; The sign, I’ll just change it to _.

a& B – & gt; a_b

Delete the.imL file in the project with the same name as the project name and reimport it. Problem solving.

A&amp was deleted from the project; B.i ml file.

    Macintosh:Permissions 0755 for '/User/xxxx/.ssh/id_rsa' are too open.
    Linux:Permissions 0755 for '/home/xxxx/.ssh/id_rsa' are too open.

This means that your private key permissions are too large, so only you need to operate

    sudo chmod 600 ~/.ssh/id_rsa sudo chmod 600 ~/.ssh/id_rsa.pub

The known_hosts file has a problem with permissions when you encounter the following situation

    Are you sure you want to continue connecting (yes/no)?yes Failed to add the host to the list of known hosts

Execute this command

    sudo chmod 644 ~/.ssh/known_hosts

Finally, to get your.ssh folder permissions right, execute the following command

    sudo chmod 755 ~/.ssh

Then your.ssh folder and the private and public key permissions within it are resolved!

[INFO] Scanning for projects...
[INFO] Downloading from nexus: http://maven.aliyun.com/nexus/content/groups/public/com/bonc/ti/ti-parent/1.0.6-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata com.bonc.ti:ti-parent:1.0.6-SNAPSHOT/maven-metadata.xml from/to nexus (http://maven.aliyun.com/nexus/content/groups/public/): Operation not supported: connect
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Building vbap data model 3.0.7-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading from nexus: http://maven.aliyun.com/nexus/content/groups/public/org/apache/maven/plugins/maven-install-plugin/2.5.2/maven-install-plugin-2.5.2.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.307 s
[INFO] Finished at: 2017-12-19T19:50:31+08:00
[INFO] Final Memory: 15M/155M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-install-plugin:2.5.2 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-install-plugin:jar:2.5.2: Could not transfer artifact org.apache.maven.plugins:maven-install-plugin:pom:2.5.2 from/to nexus (http://maven.aliyun.com/nexus/content/groups/public/): Operation not supported: connect -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

The maven-install-Plugin :2.5.2 shows that it is not possible to transfer the Maven-install-plugin from the repository, because When Maven installs, it is done through the Maven-install-Plugin. The existence of the install plugin must be ensured first. Visit http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException you can see the cause of abnormal PluginResolutionException this has six:
 
 
 
1. Trying to access a plug-in that doesn't exist in the repository, such as miswriting the Group ID, artifact ID, or version number.
2. The accessed plug-in is a third-party plug-in not published to the central library, but your pom file or setting.xml file does not have < pluginRepository> The tag indicates the plug-in to be downloaded from the repository. One thing to note here is that < repository> definition does not work when finding plug-ins and their dependencies, only < pluginRepository> works for the plug-in download.
3. The plug-in repository needs permission authentication, but Maven does not have permission authentication, so it cannot access the repository server, so it should go to < server> definition:

<server>
  <!-- server（服务器）的id,对应着mirrors中的id，指定了该地址的验证信息 -->
  <id>nexus</id>
  <username>xxx</username>
  <password>xxx</password>
</server>

<proxies>
 <proxy>
  <id>optional</id>
  <active>true</active>
  <protocol>http</protocol>
  <host>代理的ip地址</host>
  <port>端口</port>
 </proxy>
</proxies>

<pluginRepositories>
  <pluginRepository>
    <id>central</id>
    <url>http://central</url>
    <releases>
      <enabled>true</enabled>
    </releases>
    <snapshots>
      <enabled>true</enabled>
    </snapshots>
  </pluginRepository>
</pluginRepositories>