1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document use of android:allowNativeHeapPointerTagging in the manifest

Browse Source 
Document the tag for more clarity on why it's needed, and for what
platforms.

Pick-to: 6.2 6.3
Task-number: QTBUG-97009
Task-number: QTBUG-91150
Change-Id: Ie4522fb582583be07270d3cdbf83992897b51669
Reviewed-by: Nicholas Bennett <nicholas.bennett@qt.io>
This commit is contained in:
Assam Boudjelthia 2022-03-03 12:26:31 +02:00
parent 42aa0028b7
commit 1956ca7d70
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/global/externalsites/external-resources.qdoc
View File

@ -52,6 +52,10 @@
\externalpage https://developer.android.com/training/app-links/verify-site-associations
\title Android: Verify Android App Links
*/
/*!
\externalpage https://source.android.com/devices/tech/debug/tagged-pointers
\title Android: Tagged Pointers
*/
/*!
\externalpage https://developer.apple.com/documentation/uikit/uiapplication/1622952-canopenurl
\title iOS: canOpenURL:

7
src/android/templates/doc/src/android-manifest-file-configuration.qdoc
View File

@ -108,6 +108,13 @@ Qt sets the following manifest configuration by default:
\row
\li android:requestLegacyExternalStorage
\li Whether to use Android scoped storage. Default \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 {1, 6} \l {Android: App Manifest <activity>}{<activity>}
\li android:name