1945 lines
130 KiB
XML
1945 lines
130 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<issues format="6" by="lint 9.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 or sdk runs on a version of Android that is more recent than your `targetSdk` 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 `targetSdk` is less than 14, your app may get an option button in the UI.

To fix this issue, set the `targetSdk` 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 35"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="13"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="FragmentTagUsage"
|
|
severity="Warning"
|
|
message="Replace the <fragment> tag with FragmentContainerView."
|
|
category="Correctness"
|
|
priority="5"
|
|
summary="Use FragmentContainerView instead of the <fragment> tag"
|
|
explanation="FragmentContainerView replaces the <fragment> tag as the preferred way of adding fragments via XML. Unlike the <fragment> tag, FragmentContainerView uses a normal `FragmentTransaction` under the hood to add the initial fragment, allowing further FragmentTransaction operations on the FragmentContainerView and providing a consistent timing for lifecycle events."
|
|
url="https://developer.android.com/reference/androidx/fragment/app/FragmentContainerView.html"
|
|
urls="https://developer.android.com/reference/androidx/fragment/app/FragmentContainerView.html"
|
|
errorLine1=" <fragment"
|
|
errorLine2=" ~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_main.xml"
|
|
line="9"
|
|
column="6"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="AndroidGradlePluginVersion"
|
|
severity="Warning"
|
|
message="A newer version of Gradle than 9.3.1 is available: 9.4.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Obsolete Android Gradle Plugin Version"
|
|
explanation="This detector looks for usage of the Android Gradle Plugin 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="distributionUrl=https\://services.gradle.org/distributions/gradle-9.3.1-bin.zip"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/gradle/wrapper/gradle-wrapper.properties"
|
|
line="3"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of `compileSdk` than 35 is available: 36"
|
|
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=" compileSdk 35"
|
|
errorLine2=" ~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="8"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.appcompat:appcompat than 1.6.1 is available: 1.7.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.appcompat:appcompat:1.6.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="39"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.android.material:material than 1.11.0 is available: 1.13.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.11.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="40"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.constraintlayout:constraintlayout than 2.1.4 is available: 2.2.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.constraintlayout:constraintlayout:2.1.4'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="41"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.lifecycle:lifecycle-livedata-ktx than 2.7.0 is available: 2.10.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 'androidx.lifecycle:lifecycle-livedata-ktx:2.7.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="42"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.lifecycle:lifecycle-viewmodel-ktx than 2.7.0 is available: 2.10.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 'androidx.lifecycle:lifecycle-viewmodel-ktx:2.7.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="43"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.navigation:navigation-fragment than 2.7.7 is available: 2.9.7"
|
|
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.navigation:navigation-fragment:2.7.7'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="44"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.navigation:navigation-ui than 2.7.7 is available: 2.9.7"
|
|
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.navigation:navigation-ui:2.7.7'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="45"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.android.libraries.identity.googleid:googleid than 1.1.1 is available: 1.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.android.libraries.identity.googleid:googleid:1.1.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="51"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.test.ext:junit than 1.1.5 is available: 1.3.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=" androidTestImplementation 'androidx.test.ext:junit:1.1.5'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="55"
|
|
column="31"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of androidx.test.espresso:espresso-core than 3.5.1 is available: 3.7.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=" androidTestImplementation 'androidx.test.espresso:espresso-core:3.5.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="56"
|
|
column="31"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.android.gms:play-services-location than 21.0.1 is available: 21.3.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.gms:play-services-location:21.0.1'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="59"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDependency"
|
|
severity="Warning"
|
|
message="A newer version of com.google.firebase:firebase-bom than 32.7.2 is available: 34.10.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 platform('com.google.firebase:firebase-bom:32.7.2')"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="73"
|
|
column="29"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="GradleDynamicVersion"
|
|
severity="Warning"
|
|
message="Avoid using + in version numbers; can lead to unpredictable and unrepeatable builds (com.google.ai.client.generativeai:generativeai:+)"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Gradle Dynamic Version"
|
|
explanation="Using `+` in dependencies lets you automatically pick up the latest available version rather than a specific, named version. However, this is not recommended; your builds are not repeatable; you may have tested with a slightly different version than what the build server used. (Using a dynamic version as the major version number is more problematic than using it in the minor version position.)"
|
|
errorLine1=" implementation 'com.google.ai.client.generativeai:generativeai:+'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="62"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.google.guava:guava than 31.1-android is available: 33.5.0-android"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="This detector checks with a central repository to see if there are newer versions available for the dependencies used by this project. This is similar to the `GradleDependency` check, which checks for newer versions available in the Android SDK tools and libraries, but this works with any MavenCentral dependency, and connects to the library every time, which makes it more flexible but also **much** slower."
|
|
errorLine1=" implementation 'com.google.guava:guava:31.1-android'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="65"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.squareup.retrofit2:retrofit than 2.9.0 is available: 3.0.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="This detector checks with a central repository to see if there are newer versions available for the dependencies used by this project. This is similar to the `GradleDependency` check, which checks for newer versions available in the Android SDK tools and libraries, but this works with any MavenCentral dependency, and connects to the library every time, which makes it more flexible but also **much** slower."
|
|
errorLine1=" implementation 'com.squareup.retrofit2:retrofit:2.9.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="68"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.squareup.retrofit2:converter-gson than 2.9.0 is available: 3.0.0"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="This detector checks with a central repository to see if there are newer versions available for the dependencies used by this project. This is similar to the `GradleDependency` check, which checks for newer versions available in the Android SDK tools and libraries, but this works with any MavenCentral dependency, and connects to the library every time, which makes it more flexible but also **much** slower."
|
|
errorLine1=" implementation 'com.squareup.retrofit2:converter-gson:2.9.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="69"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="NewerVersionAvailable"
|
|
severity="Warning"
|
|
message="A newer version of com.squareup.okhttp3:okhttp than 4.10.0 is available: 5.3.2"
|
|
category="Correctness"
|
|
priority="4"
|
|
summary="Newer Library Versions Available"
|
|
explanation="This detector checks with a central repository to see if there are newer versions available for the dependencies used by this project. This is similar to the `GradleDependency` check, which checks for newer versions available in the Android SDK tools and libraries, but this works with any MavenCentral dependency, and connects to the library every time, which makes it more flexible but also **much** slower."
|
|
errorLine1=" implementation 'com.squareup.okhttp3:okhttp:4.10.0'"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/build.gradle"
|
|
line="70"
|
|
column="20"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DisableBaselineAlignment"
|
|
severity="Warning"
|
|
message="Set `android:baselineAligned="false"` on this element for better performance"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Missing `baselineAligned` attribute"
|
|
explanation="When a `LinearLayout` is used to distribute the space proportionally between nested layouts, the baseline alignment property should be turned off to make the layout computation faster."
|
|
errorLine1=" <LinearLayout"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="59"
|
|
column="18"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="DisableBaselineAlignment"
|
|
severity="Warning"
|
|
message="Set `android:baselineAligned="false"` on this element for better performance"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Missing `baselineAligned` attribute"
|
|
explanation="When a `LinearLayout` is used to distribute the space proportionally between nested layouts, the baseline alignment property should be turned off to make the layout computation faster."
|
|
errorLine1=" <LinearLayout"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register_medico.xml"
|
|
line="59"
|
|
column="18"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="If you set a background drawable on a root view, then you should use a custom theme where the theme background is null. Otherwise, the theme background will be painted first, only to have your custom background completely cover it; this is called "overdraw".

NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.

If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.

Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="8"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="If you set a background drawable on a root view, then you should use a custom theme where the theme background is null. Otherwise, the theme background will be painted first, only to have your custom background completely cover it; this is called "overdraw".

NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.

If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.

Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_login.xml"
|
|
line="7"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="If you set a background drawable on a root view, then you should use a custom theme where the theme background is null. Otherwise, the theme background will be painted first, only to have your custom background completely cover it; this is called "overdraw".

NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.

If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.

Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="7"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="If you set a background drawable on a root view, then you should use a custom theme where the theme background is null. Otherwise, the theme background will be painted first, only to have your custom background completely cover it; this is called "overdraw".

NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.

If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.

Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register_medico.xml"
|
|
line="7"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="Overdraw"
|
|
severity="Warning"
|
|
message="Possible overdraw: Root element paints background `@color/background_color` with a theme that also paints a background (inferred theme is `@style/Theme.Cuida`)"
|
|
category="Performance"
|
|
priority="3"
|
|
summary="Overdraw: Painting regions more than once"
|
|
explanation="If you set a background drawable on a root view, then you should use a custom theme where the theme background is null. Otherwise, the theme background will be painted first, only to have your custom background completely cover it; this is called "overdraw".

NOTE: This detector relies on figuring out which layouts are associated with which activities based on scanning the Java code, and it's currently doing that using an inexact pattern matching algorithm. Therefore, it can incorrectly conclude which activity the layout is associated with and then wrongly complain that a background-theme is hidden.

If you want your custom background on multiple pages, then you should consider making a custom theme with your custom background and just using that theme instead of a root element background.

Of course it's possible that your custom drawable is translucent and you want it to be mixed with the background. However, you will get better performance if you pre-mix the background with your drawable and use that resulting image or color as a custom theme background instead."
|
|
errorLine1=" android:background="@color/background_color">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="9"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.activity_forgot_password` 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="<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.activity_register` 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="<ScrollView xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.btn_outline_error` 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="<ripple xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/btn_outline_error.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.btn_outline_primary` 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="<ripple xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/btn_outline_primary.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.primary_light_color` 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="primary_light_color">#E3F2FD</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="5"
|
|
column="12"/>
|
|
</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">#90CAF9</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="18"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.purple_500` 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_500">#0066CC</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="19"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.purple_700` 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_700">#004C99</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="20"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.color.teal_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="teal_200">#69F0AE</color>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/values/colors.xml"
|
|
line="21"
|
|
column="12"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.dialog_add_medication` 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="<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.dialog_change_password` 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="<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.dialog_edit_profile` 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="<ScrollView xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_launcher` 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="<vector xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_launcher.xml"
|
|
line="1"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.drawable.ic_launcher_round` 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="<vector xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_launcher_round.xml"
|
|
line="1"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.item_appointment` 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="<com.google.android.material.card.MaterialCardView xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_appointment.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.item_medication` 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="<com.google.android.material.card.MaterialCardView xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_medication.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UnusedResources"
|
|
severity="Warning"
|
|
message="The resource `R.layout.item_time_slot` 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="<com.google.android.material.button.MaterialButton xmlns:android="http://schemas.android.com/apk/res/android""
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_time_slot.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="UselessParent"
|
|
severity="Warning"
|
|
message="This `LinearLayout` layout or its `FrameLayout` parent is unnecessary"
|
|
category="Performance"
|
|
priority="2"
|
|
summary="Unnecessary parent layout"
|
|
explanation="A layout with children that has no siblings, is not a scrollview or a root layout, and does not have a background, can be removed and have its children moved directly into the parent for a flatter and more efficient layout hierarchy."
|
|
errorLine1=" <LinearLayout"
|
|
errorLine2=" ~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_appointments.xml"
|
|
line="6"
|
|
column="6"/>
|
|
</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="The system may use the coloring of the user's chosen wallpaper and theme to tint app icons. Providing a `<monochrome>` layer (which will be used for tinting) for every adaptive icon is strongly recommended, otherwise Android 16 QPR 2 and above will simply tint the color version of the icon, which may look unusual. Devices running earlier Android versions will (with no monochrome layer) show the untinted color icon for your app, which will look inconsistent."
|
|
errorLine1="<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">"
|
|
errorLine2="^">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable-v26/ic_launcher_final.xml"
|
|
line="2"
|
|
column="1"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconLocation"
|
|
severity="Warning"
|
|
message="Found bitmap drawable `res/drawable/.!2449!ic_logo.png` in densityless folder"
|
|
category="Usability:Icons"
|
|
priority="5"
|
|
summary="Image defined in density-independent drawable folder"
|
|
explanation="The res/drawable folder is intended for density-independent graphics such as shapes defined in XML. For bitmaps, move it to `drawable-mdpi` and consider providing higher and lower resolution versions in `drawable-ldpi`, `drawable-hdpi` and `drawable-xhdpi`. If the icon **really** is density independent (for example a solid color) you can place it in `drawable-nodpi`."
|
|
url="https://developer.android.com/guide/practices/screens_support.html"
|
|
urls="https://developer.android.com/guide/practices/screens_support.html">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/.!2449!ic_logo.png"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="IconLocation"
|
|
severity="Warning"
|
|
message="Found bitmap drawable `res/drawable/ic_logo.png` in densityless folder"
|
|
category="Usability:Icons"
|
|
priority="5"
|
|
summary="Image defined in density-independent drawable folder"
|
|
explanation="The res/drawable folder is intended for density-independent graphics such as shapes defined in XML. For bitmaps, move it to `drawable-mdpi` and consider providing higher and lower resolution versions in `drawable-ldpi`, `drawable-hdpi` and `drawable-xhdpi`. If the icon **really** is density independent (for example a solid color) you can place it in `drawable-nodpi`."
|
|
url="https://developer.android.com/guide/practices/screens_support.html"
|
|
urls="https://developer.android.com/guide/practices/screens_support.html">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/drawable/ic_logo.png"/>
|
|
</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="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="10"
|
|
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="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_medication.xml"
|
|
line="20"
|
|
column="10"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="LabelFor"
|
|
severity="Warning"
|
|
message="Missing accessibility label: provide either a view with an `android:labelFor` that references this view or provide an `android:hint`"
|
|
category="Accessibility"
|
|
priority="2"
|
|
summary="Missing accessibility label"
|
|
explanation="Editable text fields should provide an `android:hint` or, provided your `minSdkVersion` is at least 17, they may be referenced by a view with a `android:labelFor` attribute.

When using `android:labelFor`, be sure to provide an `android:text` or an `android:contentDescription`.

If your view is labeled but by a label in a different layout which includes this one, just suppress this warning from lint."
|
|
errorLine1=" <AutoCompleteTextView"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="105"
|
|
column="22"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="LabelFor"
|
|
severity="Warning"
|
|
message="Missing accessibility label: provide either a view with an `android:labelFor` that references this view or provide an `android:hint`"
|
|
category="Accessibility"
|
|
priority="2"
|
|
summary="Missing accessibility label"
|
|
explanation="Editable text fields should provide an `android:hint` or, provided your `minSdkVersion` is at least 17, they may be referenced by a view with a `android:labelFor` attribute.

When using `android:labelFor`, be sure to provide an `android:text` or an `android:contentDescription`.

If your view is labeled but by a label in a different layout which includes this one, just suppress this warning from lint."
|
|
errorLine1=" <AutoCompleteTextView"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register_medico.xml"
|
|
line="105"
|
|
column="22"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="LabelFor"
|
|
severity="Warning"
|
|
message="Missing accessibility label: provide either a view with an `android:labelFor` that references this view or provide an `android:hint`"
|
|
category="Accessibility"
|
|
priority="2"
|
|
summary="Missing accessibility label"
|
|
explanation="Editable text fields should provide an `android:hint` or, provided your `minSdkVersion` is at least 17, they may be referenced by a view with a `android:labelFor` attribute.

When using `android:labelFor`, be sure to provide an `android:text` or an `android:contentDescription`.

If your view is labeled but by a label in a different layout which includes this one, just suppress this warning from lint."
|
|
errorLine1=" <AutoCompleteTextView"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="64"
|
|
column="10"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Insira o seu email para recuperar a palavra-passe.", 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="Insira o seu email para recuperar a palavra-passe.""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="29"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Recuperar Palavra-passe", 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="Recuperar Palavra-passe""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="51"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Voltar ao Login", 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="Voltar ao Login""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_forgot_password.xml"
|
|
line="59"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Lembrar-me", 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="Lembrar-me""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_login.xml"
|
|
line="78"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nº Utente", 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="Nº Utente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="92"
|
|
column="29"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Sexo", 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="Sexo">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register.xml"
|
|
line="103"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nº Utente", 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="Nº Utente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register_medico.xml"
|
|
line="92"
|
|
column="29"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Sexo", 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="Sexo">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/activity_register_medico.xml"
|
|
line="103"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome do Medicamento", 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="Nome do Medicamento""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="11"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Horário", 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="Horário""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="22"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "08:00", 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="08:00""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="32"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Via de Administração", 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="Via de Administração""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="40"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Via Oral (Pela boca)", 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="Via Oral (Pela boca)" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="56"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Via Tópica (Na pele)", 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="Via Tópica (Na pele)" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="62"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Via Inalatória (Pelo nariz/boca)", 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="Via Inalatória (Pelo nariz/boca)" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="68"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Notas (Opcional)", 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="Notas (Opcional)""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_add_medication.xml"
|
|
line="74"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Alterar Palavra-passe", 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="Alterar Palavra-passe""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="11"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nova Palavra-passe", 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="Nova Palavra-passe""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="26"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Cancelar", 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="Cancelar""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="41"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Salvar", 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="Salvar" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_change_password.xml"
|
|
line="48"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Mudar Foto", 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="Mudar Foto""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="31"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Editar Dados", 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="Editar Dados""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="37"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome", 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="Nome""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="52"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Idade", 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="Idade""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="65"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nº Utente", 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="Nº Utente""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="79"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Email", 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="Email""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="93"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Alterar Palavra-passe", 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="Alterar Palavra-passe""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="103"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Cancelar", 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="Cancelar""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="117"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Salvar", 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="Salvar" />"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/dialog_edit_profile.xml"
|
|
line="124"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Futuras", 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="Futuras""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_appointments.xml"
|
|
line="25"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Passadas", 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="Passadas""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_appointments.xml"
|
|
line="38"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Olá, utilizador!", 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="Olá, utilizador!""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_home.xml"
|
|
line="12"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Próxima Medicação", 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="Próxima Medicação""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_home.xml"
|
|
line="40"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Paracetamol 500mg", 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="Paracetamol 500mg""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_home.xml"
|
|
line="49"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Hoje, 14:00", 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="Hoje, 14:00""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_home.xml"
|
|
line="57"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Marcar Consulta", 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="Marcar Consulta""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_home.xml"
|
|
line="68"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Ainda não tem medicamentos guardados.", 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="Ainda não tem medicamentos guardados.""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_medication.xml"
|
|
line="34"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Adicionar Medicamento", 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:contentDescription="Adicionar Medicamento"/>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_medication.xml"
|
|
line="52"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome do Utilizador", 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="Nome do Utilizador""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="39"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "email@exemplo.com", 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="email@exemplo.com""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="49"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Idade: ", 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="Idade: ""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="70"
|
|
column="21"/>
|
|
</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="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="78"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nº Utente: ", 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="Nº Utente: ""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="93"
|
|
column="21"/>
|
|
</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="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="101"
|
|
column="21"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Editar Dados", 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="Editar Dados""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="114"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Terminar Sessão", 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="Terminar Sessão""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_profile.xml"
|
|
line="123"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Agendar Consulta", 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="Agendar Consulta""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="11"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Selecionar Data", 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="Selecionar Data""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="20"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Selecionar Horário", 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="Selecionar Horário""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="37"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Selecionar Médico/Especialidade", 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="Selecionar Médico/Especialidade""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="52"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Escolha o médico", 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="Escolha o médico">"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="62"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Motivo da Consulta", 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="Motivo da Consulta""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="81"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Confirmar Agendamento", 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="Confirmar Agendamento"/>"
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_schedule_appointment.xml"
|
|
line="91"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Ligar SNS 24 (808 24 24 24)", 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="Ligar SNS 24 (808 24 24 24)""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_sns24.xml"
|
|
line="23"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Triagem com Inteligência Artificial", 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="Triagem com Inteligência Artificial""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_sns24.xml"
|
|
line="39"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Descreva o que está a sentir...", 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="Descreva o que está a sentir...""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_sns24.xml"
|
|
line="48"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Analisar Sintomas", 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="Analisar Sintomas""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_sns24.xml"
|
|
line="65"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Hospital mais próximo", 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="Hospital mais próximo""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/fragment_sns24.xml"
|
|
line="85"
|
|
column="9"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Tipo de Consulta", 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="Tipo de Consulta""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_appointment.xml"
|
|
line="23"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "dd/MM/yyyy", 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="dd/MM/yyyy""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_appointment.xml"
|
|
line="38"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "HH:mm", 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="HH:mm""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_appointment.xml"
|
|
line="45"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Motivo: --", 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="Motivo: --""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_appointment.xml"
|
|
line="53"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Nome Medicamento", 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="Nome Medicamento""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_medication.xml"
|
|
line="37"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Dosagem", 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="Dosagem""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_medication.xml"
|
|
line="46"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "Observações", 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="Observações""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_medication.xml"
|
|
line="53"
|
|
column="17"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "HH:mm", 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="HH:mm""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_medication.xml"
|
|
line="63"
|
|
column="13"/>
|
|
</issue>
|
|
|
|
<issue
|
|
id="HardcodedText"
|
|
severity="Warning"
|
|
message="Hardcoded string "09:00", 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="09:00""
|
|
errorLine2=" ~~~~~~~~~~~~~~~~~~~~">
|
|
<location
|
|
file="/Users/230405/Desktop/med Cuida+/app/src/main/res/layout/item_time_slot.xml"
|
|
line="6"
|
|
column="5"/>
|
|
</issue>
|
|
|
|
</issues>
|