F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\AndroidManifest.xml:8: Warning: READ_EXTERNAL_STORAGE is deprecated (and is not granted) when targeting Android 13+. If you need to query or interact with MediaStore or media files on the shared storage, you should instead use one or more new storage permissions: READ_MEDIA_IMAGES, READ_MEDIA_VIDEO or READ_MEDIA_AUDIO. [ScopedStorage]
  <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\AndroidManifest.xml:9: Warning: WRITE_EXTERNAL_STORAGE is deprecated (and is not granted) when targeting Android 13+. If you need to write to shared storage, use the MediaStore.createWriteRequest intent. [ScopedStorage]
  <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "ScopedStorage":
   Scoped storage is enforced on Android 10+ (or Android 11+ if using
   requestLegacyExternalStorage). In particular, WRITE_EXTERNAL_STORAGE will
   no longer provide write access to all files; it will provide the equivalent
   of READ_EXTERNAL_STORAGE instead.

   As of Android 13, if you need to query or interact with MediaStore or media
   files on the shared storage, you should be using instead one or more new
   storage permissions:
   * android.permission.READ_MEDIA_IMAGES
   * android.permission.READ_MEDIA_VIDEO
   * android.permission.READ_MEDIA_AUDIO

   and then add maxSdkVersion="33" to the older permission. See the developer
   guide for how to do this:
   https://developer.android.com/about/versions/13/behavior-changes-13#granula
   r-media-permissions

   The MANAGE_EXTERNAL_STORAGE permission can be used to manage all files, but
   it is rarely necessary and most apps on Google Play are not allowed to use
   it. Most apps should instead migrate to use scoped storage. To modify or
   delete files, apps should request write access from the user as described
   at https://goo.gle/android-mediastore-createwriterequest.

   To learn more, read these resources: Play policy:
   https://goo.gle/policy-storage-help Allowable use cases:
   https://goo.gle/policy-storage-usecases

   https://goo.gle/android-storage-usecases

F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\AndroidManifest.xml:13: Error: Attribute is missing the Android namespace prefix [MissingPrefix]
  <uses-feature android:name="android.hardware.telephony" required="false" />
                                                          ~~~~~~~~~~~~~~~~

   Explanation for issues of type "MissingPrefix":
   Most Android views have attributes in the Android namespace. When
   referencing these attributes you must include the namespace prefix, or your
   attribute will be interpreted by aapt as just a custom attribute.

   Similarly, in manifest files, nearly all attributes should be in the
   android: namespace.

F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:12: Warning: 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. [OldTargetApi]
        targetSdk 33
        ~~~~~~~~~~~~

   Explanation for issues of type "OldTargetApi":
   When your application runs on a version of Android that is more recent than
   your targetSdkVersion specifies that it has been tested with, various
   compatibility modes kick in. This ensures that your application continues
   to work, but it may look out of place. For example, if the targetSdkVersion
   is less than 14, your app may get an option button in the UI.

   To fix this issue, set the targetSdkVersion to the highest available value.
   Then test your app to make sure everything works correctly. You may want to
   consult the compatibility notes to see what changes apply to each version
   you are adding support for:
   https://developer.android.com/reference/android/os/Build.VERSION_CODES.html
   as well as follow this guide:
   https://developer.android.com/distribute/best-practices/develop/target-sdk.
   html

   https://developer.android.com/distribute/best-practices/develop/target-sdk.html

F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\AndroidManifest.xml:14: Warning: Attribute usesCleartextTraffic is only used in API level 23 and higher (current min is 21) [UnusedAttribute]
  <application android:persistent="false" android:restoreAnyVersion="false" android:label="smeprg" android:largeHeap="false" android:icon="@mipmap/ic_launcher" android:theme="@style/AppTheme" android:usesCleartextTraffic="true" android:hardwareAccelerated="true">
                                                                                                                                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "UnusedAttribute":
   This check finds attributes set in XML files that were introduced in a
   version newer than the oldest version targeted by your application (with
   the minSdkVersion attribute).

   This is not an error; the application will simply ignore the attribute.
   However, if the attribute is important to the appearance or functionality
   of your application, you should consider finding an alternative way to
   achieve the same result with only available attributes, and then you can
   optionally create a copy of the layout in a layout-vNN folder which will be
   used on API NN or higher where you can take advantage of the newer
   attribute.

   Note: This check does not only apply to attributes. For example, some tags
   can be unused too, such as the new <tag> element in layouts introduced in
   API 21.

F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\AndroidManifest.xml:32: Warning: <uses-feature> tag appears after <application> tag [ManifestOrder]
  <uses-feature android:name="android.hardware.camera" />
   ~~~~~~~~~~~~

   Explanation for issues of type "ManifestOrder":
   The <application> tag should appear after the elements which declare which
   version you need, which features you need, which libraries you need, and so
   on. In the past there have been subtle bugs (such as themes not getting
   applied correctly) when the <application> tag appears before some of these
   other elements, so it's best to order your manifest in the logical
   dependency order.

F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:62: Warning: A newer version of com.google.android.gms:play-services-maps than 18.1.0 is available: 18.2.0 [GradleDependency]
    implementation 'com.google.android.gms:play-services-maps:18.1.0'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:67: Warning: A newer version of androidx.core:core than 1.9.0 is available: 1.12.0 [GradleDependency]
    implementation 'androidx.core:core:1.9.0'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:68: Warning: A newer version of androidx.annotation:annotation than 1.5.0 is available: 1.7.1 [GradleDependency]
    implementation 'androidx.annotation:annotation:1.5.0'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:71: Warning: A newer version of androidx.recyclerview:recyclerview than 1.2.1 is available: 1.3.2 [GradleDependency]
    implementation group: 'androidx.recyclerview', name: 'recyclerview', version: '1.2.1'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:74: Warning: A newer version of androidx.appcompat:appcompat than 1.5.1 is available: 1.6.1 [GradleDependency]
    implementation group: 'androidx.appcompat', name: 'appcompat', version: '1.5.1'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:76: Warning: A newer version of com.google.android.material:material than 1.6.1 is available: 1.11.0 [GradleDependency]
    implementation group: 'com.google.android.material', name: 'material', version: '1.6.1'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:82: Warning: A newer version of com.google.android.gms:play-services-mlkit-barcode-scanning than 18.1.0 is available: 18.3.0 [GradleDependency]
    implementation group: 'com.google.android.gms', name: 'play-services-mlkit-barcode-scanning', version: '18.1.0'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:85: Warning: A newer version of com.google.android.gms:play-services-auth than 20.3.0 is available: 21.0.0 [GradleDependency]
    implementation group: 'com.google.android.gms', name: 'play-services-auth', version: '20.3.0'
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "GradleDependency":
   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.

F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:56: Warning: Do not use Windows file separators in .gradle files; use / instead [GradlePath]
    implementation files('C:\\Users\\HP\\AppData\\Local\\FGX Native\\Libs\\Common\\Android\\Debug\\aar\\fgx.core.aar')
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:57: Warning: Do not use Windows file separators in .gradle files; use / instead [GradlePath]
    implementation files('C:\\Users\\HP\\AppData\\Local\\FGX Native\\Libs\\Common\\Android\\Debug\\aar\\fgx.androidx.aar')
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:58: Warning: Do not use Windows file separators in .gradle files; use / instead [GradlePath]
    implementation files('C:\\Users\\HP\\AppData\\Local\\FGX Native\\Libs\\Common\\Android\\Debug\\aar\\fgx.visio.aar')
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:59: Warning: Do not use Windows file separators in .gradle files; use / instead [GradlePath]
    implementation files('C:\\Users\\HP\\AppData\\Local\\FGX Native\\Libs\\Common\\Android\\Debug\\aar\\fgx.googlesignin.aar')
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:60: Warning: Do not use Windows file separators in .gradle files; use / instead [GradlePath]
    implementation files('C:\\Users\\HP\\AppData\\Local\\FGX Native\\Libs\\Common\\Android\\Debug\\aar\\fgx.googlemap.aar')
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
F:\Delphi_FGX_11\SomePrg\.android-build\app\build.gradle:61: Warning: Do not use Windows file separators in .gradle files; use / instead [GradlePath]
    implementation files('C:\\Users\\HP\\AppData\\Local\\FGX Native\\Libs\\Common\\Android\\Debug\\aar\\fgx.googlemap.aar')
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "GradlePath":
   Gradle build scripts are meant to be cross platform, so file paths use
   Unix-style path separators (a forward slash) rather than Windows path
   separators (a backslash). Similarly, to keep projects portable and
   repeatable, avoid using absolute paths on the system; keep files within the
   project instead. To share code between projects, consider creating an
   android-library and an AAR dependency

F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\drawable-xxxhdpi\ic_launcher.png: Warning: The resource R.drawable.ic_launcher appears to be unused [UnusedResources]
F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\mipmap-hdpi\ic_launcher_round.png: Warning: The resource R.mipmap.ic_launcher_round appears to be unused [UnusedResources]
F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\mipmap-hdpi\ic_notification.png: Warning: The resource R.mipmap.ic_notification appears to be unused [UnusedResources]
F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\values\styles.xml:37: Warning: The resource R.style.CollectionView appears to be unused [UnusedResources]
    <style name="CollectionView" parent="android:Widget">
           ~~~~~~~~~~~~~~~~~~~~~

   Explanation for issues of type "UnusedResources":
   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.
   ,

F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\drawable-xxxhdpi\ic_launcher.png: Warning: Launcher icons should not fill every pixel of their square region; see the design guide for details [IconLauncherShape]

   Explanation for issues of type "IconLauncherShape":
   According to the Android Design Guide
   (https://d.android.com/r/studio-ui/designer/material/iconography) your
   launcher icons should "use a distinct silhouette", a "three-dimensional,
   front view, with a slight perspective as if viewed from above, so that
   users perceive some depth."

   The unique silhouette implies that your launcher icon should not be a
   filled square.

F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\drawable-hdpi: Warning: Missing the following drawables in drawable-hdpi: ic_launcher.png (found in drawable-xxxhdpi) [IconDensities]
F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\drawable-mdpi: Warning: Missing the following drawables in drawable-mdpi: ic_launcher.png (found in drawable-xxxhdpi) [IconDensities]
F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res\drawable-xhdpi: Warning: Missing the following drawables in drawable-xhdpi: ic_launcher.png (found in drawable-xxxhdpi) [IconDensities]

   Explanation for issues of type "IconDensities":
   Icons will look best if a custom version is provided for each of the major
   screen density classes (low, medium, high, extra high). This lint check
   identifies icons which do not have complete coverage across the densities.

   Low density is not really used much anymore, so this check ignores the ldpi
   density. To force lint to include it, set the environment variable
   ANDROID_LINT_INCLUDE_LDPI=true. For more information on current density
   usage, see https://developer.android.com/about/dashboards

   https://developer.android.com/guide/practices/screens_support.html

F:\Delphi_FGX_11\SomePrg\.android-build\app\src\main\res: Warning: Missing density variation folders in src\main\res: drawable-xxhdpi [IconMissingDensityFolder]

   Explanation for issues of type "IconMissingDensityFolder":
   Icons will look best if a custom version is provided for each of the major
   screen density classes (low, medium, high, extra-high, extra-extra-high).
   This lint check identifies folders which are missing, such as
   drawable-hdpi.

   Low density is not really used much anymore, so this check ignores the ldpi
   density. To force lint to include it, set the environment variable
   ANDROID_LINT_INCLUDE_LDPI=true. For more information on current density
   usage, see https://developer.android.com/about/dashboards

   https://developer.android.com/guide/practices/screens_support.html

1 errors, 28 warnings