|
|
2018-05-15 02:26:06
/uzmap/temp/DWXY1kmfU1C70H0/AStudioProject/app/src/main/AndroidManifest.xml:34: Error: Avoid hardcoding the debug mode; leaving it out allows debug and release builds to automatically assign one [HardcodedDebugMode]
<application android:allowBackup="false" android:debuggable="false" android:hardwareAccelerated="true" android:icon="@drawable/uz_icon" android:label="@string/app_name" android:largeHeap="true" android:name="com.uzmap.pkg.uzapp.UZApplication" tools:replace="android:icon,android:debuggable,android:allowBackup">
~~~~~~~~~~~~~~~~~~~~~~~~~~
Explanation for issues of type "HardcodedDebugMode":
It's best to leave out the android:debuggable attribute from the manifest.
If you do, then the tools will automatically insert android:debuggable=true
when building an APK to debug on an emulator or device. And when you
perform a release build, such as Exporting APK, it will automatically set
it to false.
If on the other hand you specify a specific value in the manifest file,
then the tools will always use it. This can lead to accidentally publishing
your app with debug information.
1 errors, 0 warnings
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:transformClassesWithJarMergingForRelease'.
> com.android.build.api.transform.TransformException: java.util.zip.ZipException: duplicate entry: android/support/annotation/IntegerRes.class
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
怎么解 在线等 |
|
