:app:validateSigningProductionRelease
:app:packageProductionRelease
:app:crashlyticsStoreDeobsProductionRelease
:app:crashlyticsUploadDeobsProductionRelease
/Users/wangliang/BMW/bmw-sfm-android-master@c2be1242fcc/app/src/main/res/values/strings.xml:138: Error: "date_error_future" is not translated in "zh" (Chinese) [MissingTranslation]
<string name="date_error_future">Date cannot be in the future.</string>
~~~~~~~~~~~~~~~~~~~~~~~~
/Users/wangliang/BMW/bmw-sfm-android-master@c2be1242fcc/app/src/main/res/values/strings.xml:266: Error: "test_drive_route" is not translated in "zh" (Chinese) [MissingTranslation]
<string name="test_drive_route">Test Drive Route:</string>
~~~~~~~~~~~~~~~~~~~~~~~
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 <string> 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 <resources> element in your resource file. (The tools prefix
refers to the namespace declaration http://schemas.android.com/tools.)
2 errors, 0 warnings
:app:lintVitalProductionRelease
:app:assembleProductionRelease
:app:assembleRelease
BUILD SUCCESSFUL in 7m 28s