You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
481 lines
33 KiB
481 lines
33 KiB
<?xml version="1.0" encoding="UTF-8"?>
|
|
<issues format="6" by="lint 8.1.0">
|
|
|
|
<issue
|
|
id="OldTargetApi"
|
|
severity="Warning"
|
|
message="Not targeting the latest versions of Android; compatibility modes apply. Consider testing and updating this version. Consult the android.os.Build.VERSION_CODES javadoc for details."
|
|
category="Correctness"
|
|
priority="6"
|
|
summary="Target SDK attribute is not targeting latest version"
|
|
explanation="When your application runs on a version of Android that is more recent than your `targetSdkVersion` specifies that it has been tested with, various compatibility modes kick in. This ensures that your application continues to work, but it may look out of place. For example, if the `targetSdkVersion` is less than 14, your app may get an option button in the UI.

To fix this issue, set the `targetSdkVersion` to the highest available value. Then test your app to make sure everything works correctly. You may want to consult the compatibility notes to see what changes apply to each version you are adding support for: https://developer.android.com/reference/android/os/Build.VERSION_CODES.html as well as follow this guide:
https://developer.android.com/distribute/best-practices/develop/target-sdk.html"
|
|
url="https://developer.android.com/distribute/best-practices/develop/target-sdk.html"
|
|
urls="https://developer.android.com/distribute/best-practices/develop/target-sdk.html,https://developer.android.com/reference/android/os/Build.VERSION_CODES.html"
|
|
errorLine1=" targetSdk 33"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\build.gradle"
|
|
line="12"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.android.material:material than 1.9.0 is available: 1.11.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find."
|
|
errorLine1=" implementation 'com.google.android.material:material:1.9.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\build.gradle"
|
|
line="37"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.camera:camera-core than 1.2.3 is available: 1.3.1"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find."
|
|
errorLine1=" implementation "androidx.camera:camera-core:${camerax_version}""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\build.gradle"
|
|
line="42"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.camera:camera-camera2 than 1.2.3 is available: 1.3.1"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find."
|
|
errorLine1=" implementation "androidx.camera:camera-camera2:${camerax_version}""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\build.gradle"
|
|
line="43"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.camera:camera-lifecycle than 1.2.3 is available: 1.3.1"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find."
|
|
errorLine1=" implementation "androidx.camera:camera-lifecycle:${camerax_version}""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\build.gradle"
|
|
line="44"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.camera:camera-view than 1.2.3 is available: 1.3.1"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find."
|
|
errorLine1=" implementation "androidx.camera:camera-view:${camerax_version}""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\build.gradle"
|
|
line="45"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.mlkit:barcode-scanning than 17.1.0 is available: 17.2.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Gradle Dependency"
|
|
explanation="This detector looks for usages of libraries where the version you are using is not the current stable release. Using older versions is fine, and there are cases where you deliberately want to stick with an older version. However, you may simply not be aware that a more recent version is available, and that is what this lint check helps find."
|
|
errorLine1=" implementation 'com.google.mlkit:barcode-scanning:17.1.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\build.gradle"
|
|
line="48"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnsafeOptInUsageError"
|
|
severity="Error"
|
|
message="This declaration is opt-in and its usage should be marked with `@androidx.camera.core.ExperimentalGetImage` or `@OptIn(markerClass = androidx.camera.core.ExperimentalGetImage.class)`"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Unsafe opt-in usage intended to be error-level severity"
|
|
explanation="This API has been flagged as opt-in with error-level severity.

Any declaration annotated with this marker is considered part of an unstable or
otherwise non-standard API surface and its call sites should accept the opt-in
aspect of it by using the `@OptIn` annotation, using the marker annotation --
effectively causing further propagation of the opt-in aspect -- or configuring
the `UnsafeOptInUsageError` check's options for project-wide opt-in.

To configure project-wide opt-in, specify the `opt-in` option value in `lint.xml`
as a comma-delimited list of opted-in annotations:

```
<lint>
 <issue id="UnsafeOptInUsageError">
 <option name="opt-in" value="com.foo.ExperimentalBarAnnotation" />
 </issue>
</lint>
```"
|
|
errorLine1=" image.getImage(),"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\java\com\example\dronerecognition\RecognitionFragment.java"
|
|
line="92"
|
|
column="35"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="PermissionImpliesUnsupportedChromeOsHardware"
|
|
severity="Error"
|
|
message="Permission exists without corresponding hardware `<uses-feature android:name="android.hardware.camera" required="false">` tag"
|
|
category="Correctness:Chrome OS"
|
|
priority="3"
|
|
summary="Permission Implies Unsupported Chrome OS Hardware"
|
|
explanation="The `<uses-permission>` element should not require a permission that implies an unsupported large screen hardware feature. Google Play assumes that certain hardware related permissions indicate that the underlying hardware features are required by default. To fix the issue, consider declaring the corresponding <uses-feature> element with `required="false"` attribute."
|
|
url="https://developer.android.com/topic/arc/manifest.html#implied-features"
|
|
urls="https://developer.android.com/topic/arc/manifest.html#implied-features"
|
|
errorLine1=" <uses-permission android:name="android.permission.CAMERA" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\AndroidManifest.xml"
|
|
line="7"
|
|
column="6"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.purple_200` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property lint.unused-resources.include-tests =true, and to exclude them (usually for performance reasons), use lint.unused-resources.exclude-tests =true.
,"
|
|
errorLine1=" <color name="purple_200">#FFBB86FC</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\values\colors.xml"
|
|
line="3"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.recognition` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property lint.unused-resources.include-tests =true, and to exclude them (usually for performance reasons), use lint.unused-resources.exclude-tests =true.
,"
|
|
errorLine1=" <string name="recognition">识别</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\values\strings.xml"
|
|
line="4"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.history` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property lint.unused-resources.include-tests =true, and to exclude them (usually for performance reasons), use lint.unused-resources.exclude-tests =true.
,"
|
|
errorLine1=" <string name="history">历史记录</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\values\strings.xml"
|
|
line="5"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.string.settings` appears to be unused"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Unused resources"
|
|
explanation="Unused resources make applications larger and slow down builds.


The unused resource check can ignore tests. If you want to include resources that are only referenced from tests, consider packaging them in a test source set instead.

You can include test sources in the unused resource check by setting the system property lint.unused-resources.include-tests =true, and to exclude them (usually for performance reasons), use lint.unused-resources.exclude-tests =true.
,"
|
|
errorLine1=" <string name="settings">设置</string>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\values\strings.xml"
|
|
line="6"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="MonochromeLauncherIcon"
|
|
severity="Warning"
|
|
message="The application adaptive icon is missing a monochrome tag"
|
|
category="Usability:Icons"
|
|
priority="6"
|
|
summary="Monochrome icon is not defined"
|
|
explanation="If `android:roundIcon` and `android:icon` are both in your manifest, you must either remove the reference to `android:roundIcon` if it is not needed; or, supply the monochrome icon in the drawable defined by the `android:roundIcon` and `android:icon` attribute.

For example, if `android:roundIcon` and `android:icon` are both in the manifest, a launcher might choose to use `android:roundIcon` over `android:icon` to display the adaptive app icon. Therefore, your themed application iconwill not show if your monochrome attribute is not also specified in `android:roundIcon`."
|
|
errorLine1="<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">"
|
|
errorLine2="^">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\mipmap-anydpi-v26\ic_launcher.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="MonochromeLauncherIcon"
|
|
severity="Warning"
|
|
message="The application adaptive roundIcon is missing a monochrome tag"
|
|
category="Usability:Icons"
|
|
priority="6"
|
|
summary="Monochrome icon is not defined"
|
|
explanation="If `android:roundIcon` and `android:icon` are both in your manifest, you must either remove the reference to `android:roundIcon` if it is not needed; or, supply the monochrome icon in the drawable defined by the `android:roundIcon` and `android:icon` attribute.

For example, if `android:roundIcon` and `android:icon` are both in the manifest, a launcher might choose to use `android:roundIcon` over `android:icon` to display the adaptive app icon. Therefore, your themed application iconwill not show if your monochrome attribute is not also specified in `android:roundIcon`."
|
|
errorLine1="<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">"
|
|
errorLine2="^">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\mipmap-anydpi-v26\ic_launcher_round.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Autofill"
|
|
severity="Warning"
|
|
message="Missing `autofillHints` attribute"
|
|
category="Usability"
|
|
priority="3"
|
|
summary="Use Autofill"
|
|
explanation="Specify an `autofillHints` attribute when targeting SDK version 26 or higher or explicitly specify that the view is not important for autofill. Your app can help an autofill service classify the data correctly by providing the meaning of each view that could be autofillable, such as views representing usernames, passwords, credit card fields, email addresses, etc.

The hints can have any value, but it is recommended to use predefined values like 'username' for a username or 'creditCardNumber' for a credit card number. For a list of all predefined autofill hint constants, see the `AUTOFILL_HINT_` constants in the `View` reference at https://developer.android.com/reference/android/view/View.html.

You can mark a view unimportant for autofill by specifying an `importantForAutofill` attribute on that view or a parent view. See https://developer.android.com/reference/android/view/View.html#setImportantForAutofill(int)."
|
|
url="https://developer.android.com/guide/topics/text/autofill.html"
|
|
urls="https://developer.android.com/guide/topics/text/autofill.html"
|
|
errorLine1=" <EditText"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_user.xml"
|
|
line="16"
|
|
column="6"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Autofill"
|
|
severity="Warning"
|
|
message="Missing `autofillHints` attribute"
|
|
category="Usability"
|
|
priority="3"
|
|
summary="Use Autofill"
|
|
explanation="Specify an `autofillHints` attribute when targeting SDK version 26 or higher or explicitly specify that the view is not important for autofill. Your app can help an autofill service classify the data correctly by providing the meaning of each view that could be autofillable, such as views representing usernames, passwords, credit card fields, email addresses, etc.

The hints can have any value, but it is recommended to use predefined values like 'username' for a username or 'creditCardNumber' for a credit card number. For a list of all predefined autofill hint constants, see the `AUTOFILL_HINT_` constants in the `View` reference at https://developer.android.com/reference/android/view/View.html.

You can mark a view unimportant for autofill by specifying an `importantForAutofill` attribute on that view or a parent view. See https://developer.android.com/reference/android/view/View.html#setImportantForAutofill(int)."
|
|
url="https://developer.android.com/guide/topics/text/autofill.html"
|
|
urls="https://developer.android.com/guide/topics/text/autofill.html"
|
|
errorLine1=" <EditText"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_user.xml"
|
|
line="24"
|
|
column="6"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="ContentDescription"
|
|
severity="Warning"
|
|
message="Missing `contentDescription` attribute on image"
|
|
category="Accessibility"
|
|
priority="3"
|
|
summary="Image without `contentDescription`"
|
|
explanation="Non-textual widgets like ImageViews and ImageButtons should use the `contentDescription` attribute to specify a textual description of the widget such that screen readers and other accessibility tools can adequately describe the user interface.

Note that elements in application screens that are purely decorative and do not provide any content or enable a user action should not have accessibility content descriptions. In this case, set their descriptions to `@null`. If your app's minSdkVersion is 16 or higher, you can instead set these graphical elements' `android:importantForAccessibility` attributes to `no`.

Note that for text fields, you should not set both the `hint` and the `contentDescription` attributes since the hint will never be shown. Just set the `hint`."
|
|
url="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
urls="https://developer.android.com/guide/topics/ui/accessibility/apps#special-cases"
|
|
errorLine1=" <ImageView"
|
|
errorLine2=" ~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_map.xml"
|
|
line="6"
|
|
column="6"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="SetTextI18n"
|
|
severity="Warning"
|
|
message="Do not concatenate text displayed with `setText`. Use resource string with placeholders."
|
|
category="Internationalization"
|
|
priority="6"
|
|
summary="TextView Internationalization"
|
|
explanation="When calling `TextView#setText`
* Never call `Number#toString()` to format numbers; it will not handle fraction separators and locale-specific digits properly. Consider using `String#format` with proper format specifications (`%d` or `%f`) instead.
* Do not pass a string literal (e.g. "Hello") to display text. Hardcoded text can not be properly translated to other languages. Consider using Android resource strings instead.
* Do not build messages by concatenating text chunks. Such messages can not be properly translated."
|
|
url="https://developer.android.com/guide/topics/resources/localization.html"
|
|
urls="https://developer.android.com/guide/topics/resources/localization.html"
|
|
errorLine1=" resultText.setText("识别结果: " + rawValue);"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\java\com\example\dronerecognition\RecognitionFragment.java"
|
|
line="101"
|
|
column="64"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "地图", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:title="地图" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\menu\bottom_navigation_menu.xml"
|
|
line="6"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "识别", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:title="识别" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\menu\bottom_navigation_menu.xml"
|
|
line="10"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "历史", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:title="历史" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\menu\bottom_navigation_menu.xml"
|
|
line="14"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "用户", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:title="用户" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\menu\bottom_navigation_menu.xml"
|
|
line="18"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "开始扫描", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:text="开始扫描""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_recognition.xml"
|
|
line="33"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "用户登录", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:text="用户登录""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_user.xml"
|
|
line="11"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "用户名", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:hint="用户名""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_user.xml"
|
|
line="20"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "密码", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:hint="密码""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_user.xml"
|
|
line="28"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "登录", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:text="登录"/>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_user.xml"
|
|
line="36"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "退出登录", should use `@string` resource"
|
|
category="Internationalization"
|
|
priority="5"
|
|
summary="Hardcoded text"
|
|
explanation="Hardcoding text attributes directly in layout files is bad for several reasons:

* When creating configuration variations (for example for landscape or portrait) you have to repeat the actual text (and keep it up to date when making changes)

* The application cannot be translated to other languages by just adding new translations for existing string resources.

There are quickfixes to automatically extract this hardcoded string into a resource lookup."
|
|
errorLine1=" android:text="退出登录""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="D:\UAV\front\DroneRecognitionApp\app\src\main\res\layout\fragment_user.xml"
|
|
line="42"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
</issues>
|