diff options
| author | Tor Arne Vestbø <tor.arne.vestbo@qt.io> | 2022-05-06 17:00:51 +0200 |
|---|---|---|
| committer | Assam Boudjelthia <assam.boudjelthia@qt.io> | 2022-11-09 14:22:29 +0200 |
| commit | ef935f6e37a24f52255e6696b85a0fa9aaa7361a (patch) | |
| tree | eed0f269293c59fa9c7fba8f3aba53871e798729 /src/corelib/configure.cmake | |
| parent | 64dc886db7af91813a19313215cb3ef6031d0cb2 (diff) | |
Plumb public permission APIs to Android backend
The lock and unlock of the Android deadlock mutex is now part
of the internal implementation instead of limited to the enum
based permission API. It is unclear why 8bca441b6f65 added
the guard only to this API and not to the string based API
as well.
The check for isBackgroundLocationApi29 has been removed,
as the logic seemingly resulted in accepting every single
permission type except location permissions if used via
the enum-based API.
Since Android's platform permission API doesn't have an
Undetermined status, we keep a hash of the status for each
permission type, and by default checkPermission() would
return Undetermined, until a requestPermission() call
is done which updates the internal hash, and after that
checkPermission() would return properly Granted/Denied.
Task-number: QTBUG-100413
Change-Id: Ia95c76af754481a281bc90198e349966c9c2da52
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
Diffstat (limited to 'src/corelib/configure.cmake')
| -rw-r--r-- | src/corelib/configure.cmake | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/corelib/configure.cmake b/src/corelib/configure.cmake index 0e625408a7..d2e8fa4205 100644 --- a/src/corelib/configure.cmake +++ b/src/corelib/configure.cmake @@ -971,7 +971,7 @@ qt_feature("permissions" PUBLIC SECTION "Utilities" LABEL "Application permissions" PURPOSE "Provides support for requesting user permission to access restricted data or APIs" - CONDITION APPLE + CONDITION APPLE OR ANDROID ) qt_configure_add_summary_section(NAME "Qt Core") qt_configure_add_summary_entry(ARGS "backtrace") |