(1) occurs at compile time
Workaround:
1. In the outermost gradle, delete the following statement
(2) occurs at compile time
Workaround:
1. In the outermost gradle, delete the following statement
(3) occurs at compile time
Workaround:
1, your project exists in Chinese name, the corresponding Chinese name in the project to English can be
(4) occurs at compile time
Workaround:
1. In your project, there are uppercase letters in res\drawable, and the corresponding uppercase letters in the project will be changed to lowercase.
(5) occurs when the Aidl file is compiled
Workaround:
1, the compilation version of the project and the version of the compilation tool is inconsistent, right-click the project open Moudle Setting--app---modified compile SDK version and build tools versions consistent
2. The package name of the Aidl file that may have been copied by you has not been modified to the current package name
(6) occurs when the permission content is copied and compiled
Workaround:
1, is the XML may appear unrecognized resource file error, is the resource file inside the error
2, sometimes in the uses-permission of a space will also report this error
(7)when the Run program occurs
Workaround:
1, check the options can be
(8) occurs when compiling after the NDK is configured
Workaround:
1, compile the NDK is best not to use Sdkmanager download Ndk-bundle, otherwise will report these errors
2, the official website Download NDK Development Kit, R9, R10 series, and then replace the long-lost NDK can be
(9) occurs when Android Studio->run
Workaround:
1, on-line program, pro-test is not the problem
According to the prompts to see the ADB port number 5037 by who occupy, through the Netstat-aon|findstr "5037" to find the corresponding PID number, then through the task Manager to find the corresponding PID number of the process, and then end it, and finally restart the ADB
2, the original selection of the default adb into our own SDK inside the ADB, pro-Test success
(Ten) created two module, where one module relies on another module and causes the problem, if the In studio, there are Modulea and Moduleb, and we want Modulea to rely on Moduleb, which may occur when the issue is run
Workaround:
1, see the Moduleb of the Build.gradle, inside can see
Replace this sentence with a
Then there is another error.
Workaround:
1, need to remove the ApplicationID in Builde.gradle-android-defaultconfig
The problem is that I changed the error when I changed the latest jar package for Bmob, and when I switched from 3.4.6 to 3.5.0, I had a compilation error.
Solution:
1. jar package conflict (finished with Non-zero exit value 2)?
The main performance is the finished with Non-zero exit value 2 error after compilation because of a jar package conflict, which could be caused by importing a jar package using compile files () in dependencies. Then there are other jars introduced using the compile ' com.xxx ' approach, which exactly refers to the jar package, which results in a duplicate reference jar package conflict. The most common is a duplicate reference to the SUPPORT-V4 package
compilation error after importing third-party dependencies (Sweetalert) in Gradle
Solution:
1, due to the import of third-party dependencies also use our application Icon Value properties, TOEFL test time specific steps such as, plus the following circled statement
An error occurred on Git Push commit to GitHub
Solution:
1, the main reason is that there is no update to the latest version of the project (git has readme.md file not downloaded)
2, first code merge, git pull--rebase Origin master, then commit code, GIT push-f Origin master
(14) After upgrading Android Studio2.3, Packaging release error
Workaround:
Add the following code to the app's Build.gradle and re-generate the signed APK
Android Development Error--android Studio encountered error issues with solution Rollup