Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
6.5.0
-
None
-
-
64db65ae9 (dev), ea64c6aec (6.5), a273ea7f4 (dev), 0df03419f (6.5), 0cae76c2a (dev), 1799b3b9c (6.5), d32e1153c (6.6)
-
2023wk16FOQtforAndroid, 2023wk18FOQtforAndroid, 2023wk20FOQtforAndroid
Description
Thanks to the change 9efaf8bae914958a09d29a4cdbf62e345f3e6369 which fixes QTBUG-103281, there is no way to specify the --release flag for normal cmake based builds anymore.
This results in debug packages being created by androiddeployqt which are not accepted by the Google PlayStore.
There was a comment added to QTBUG-103281 back in December about this already, but maybe this was just ignored, because THAT bug was closed?
I see 2 possible options here:
1) extend qt6_android_add_apk_target to add something like QT_ANDROIDDEPLOYQT_EXTRA_ARGS to its extra_args variable
2) at least detect the current build type and automatically add the missing --release flag to the androiddeployqt command line, if it's a release build
Ideally we should do both: (1) for future flexibility and (2) to unbreak all existing cmake based user code.
Attachments
Issue Links
- mentioned in
-
Page Loading...