2018-08-16 03:34:52
/uzmap/temp/o4rfwfMpl2Dj3Tw/AStudioProject/app/src/main/res/values/rc_configuration.xml:17: Error: "rc_media_message_default_save_path" is not translated in "en" (English) [MissingTranslation]
/RongCloud/Media/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/uzmap/temp/o4rfwfMpl2Dj3Tw/AStudioProject/app/src/main/res/values/rc_configuration.xml:21: Error: "rc_heartbeat_timer" is not translated in "en" (English) [MissingTranslation]
150000
~~~~~~~~~~~~~~~~~~~~~~~~~
/uzmap/temp/o4rfwfMpl2Dj3Tw/AStudioProject/app/src/main/res/values/strings.xml:4: Error: "back" is not translated in "en" (English) [MissingTranslation]
返回
~~~~~~~~~~~
/uzmap/temp/o4rfwfMpl2Dj3Tw/AStudioProject/app/src/main/res/values/strings.xml:5: Error: "confirm" is not translated in "en" (English) [MissingTranslation]
确定
~~~~~~~~~~~~~~
/uzmap/temp/o4rfwfMpl2Dj3Tw/AStudioProject/app/src/main/res/values/strings.xml:6: Error: "cancel" is not translated in "en" (English) [MissingTranslation]
取消
~~~~~~~~~~~~~
/uzmap/temp/o4rfwfMpl2Dj3Tw/AStudioProject/app/src/main/res/values/strings.xml:7: Error: "prompt" is not translated in "en" (English) [MissingTranslation]
提示
~~~~~~~~~~~~~
Explanation for issues of type "MissingTranslation":
If an application has more than one locale, then all the strings declared
in one language should also be translated in all other languages.
If the string should not be translated, you can add the attribute
translatable="false" on the element, or you can define all your
non-translatable strings in a resource file called donottranslate.xml. Or,
you can ignore the issue with a tools:ignore="MissingTranslation"
attribute.
By default this detector allows regions of a language to just provide a
subset of the strings and fall back to the standard language strings. You
can require all regions to provide a full translation by setting the
environment variable ANDROID_LINT_COMPLETE_REGIONS.
You can tell lint (and other tools) which language is the default language
in your res/values/ folder by specifying tools:locale="languageCode" for
the root element in your resource file. (The tools prefix
refers to the namespace declaration http://schemas.android.com/tools.)
/uzmap/temp/o4rfwfMpl2Dj3Tw/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]
~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
7 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: com/tencent/mm/opensdk/channel/a/a$a.class
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.