Android: remove unneeded allowNativeHeapPointerTagging manifest flag

Amends b0907db9eae4b85fcab4fa997428c438d9443ee0.

Pick-to: 6.5 6.6
Task-number: QTBUG-91150
Change-Id: Ic7886a9fc69781e4f21417075516106ccb6c7bf5
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
This commit is contained in:
Assam Boudjelthia 2023-10-20 14:32:39 +03:00
parent b419b5b65a
commit 028a31b505
4 changed files with 0 additions and 10 deletions

View File

@ -16,7 +16,6 @@
android:hardwareAccelerated="true"
android:label="-- %%INSERT_APP_NAME%% --"
android:requestLegacyExternalStorage="true"
android:allowNativeHeapPointerTagging="false"
android:allowBackup="true"
android:fullBackupOnly="false">
<activity

View File

@ -81,13 +81,6 @@ Qt sets the following manifest configuration by default:
\row
\li android:requestLegacyExternalStorage
\li Whether to use Android scoped storage. The default value is \c true.
\row
\li android:allowNativeHeapPointerTagging
\li Whether or not the app has the Heap pointer tagging feature enabled.
This has to be set to \c false when targeting Arm64 hardware with Android 11+
because it can break QML's NaN-tagging scheme.
For more information, see \l {Android: Tagged Pointers}{Tagged Pointers}.
The default value is \c false.
\row
\li android:allowBackup
\li Whether to allow the application to participate in the backup and restore

View File

@ -26,7 +26,6 @@
android:hardwareAccelerated="true"
android:label="-- %%INSERT_APP_NAME%% --"
android:requestLegacyExternalStorage="true"
android:allowNativeHeapPointerTagging="false"
android:allowBackup="true"
android:fullBackupOnly="false">
<activity

View File

@ -26,7 +26,6 @@
android:hardwareAccelerated="true"
android:label="-- %%INSERT_APP_NAME%% --"
android:requestLegacyExternalStorage="true"
android:allowNativeHeapPointerTagging="false"
android:allowBackup="true"
android:fullBackupOnly="false">
<activity