[Interest] Android Qt 6.6 -> 6.7 - Android Manifest - extract style - allowNativeHeapPointerTagging

[Assam Boudjelthia]

Hi,

For the pointerTagging, that’s removed because it’s not needed anymore as it was fixed in QTBUG-91150 but the flag was left out during the fix in 6.5 and was not needed anymore.

For 'android.app.extract_android_style', it has been set to minimal by default in a previous version after QTBUG-71590 because the Android theme on widgets is not stable making it the de facto default after that fix, and in Qt 6.7, that’s removed to keep the manifest lightweight and not have to carry that in every single app’s manifest.

So your app, should work the same way between 6.7 and 6.6 in regard to those flags.

Best regards,
Assam

16 apr. 2024 kl. 11:18 fm skrev ekke <ekke at ekkes-corner.org>:


I always create android templates to check what was changed with default Manifest between Qt versions to see if something in my customer projects must be changed.

Android Manifest Qt 6.7:

there is no entry

'android.app.extract_android_style'

In the past for QQC2 this should be set to android:value="minimal"
Without an entry it's set to default.

Has there anything changed or is it still recommended to set "minimal" ?

And there's another difference:

Manifest in 6.6 contained:

'android:allowNativeHeapPointerTagging="false"'

Manifest in 6.7 is missing this property, so it's true (default).

what is recommended ?

Is it safe without 'extract_android_style' and 'android:allowNativeHeapPointerTagging="false"'

all done with Qt 6.7 and QtC 13

thx for any info

ekke

_______________________________________________
Interest mailing list
Interest at qt-project.org
https://lists.qt-project.org/listinfo/interest

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20240416/ced3515b/attachment.htm>