Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. Extra permissions on AndroidManifest.xml
Forum Updated to NodeBB v4.3 + New Features

Extra permissions on AndroidManifest.xml

Scheduled Pinned Locked Moved Installation and Deployment
3 Posts 2 Posters 3.3k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    nikta
    wrote on last edited by
    #1

    I have a Qt5 game (https://github.com/omidnikta/qtmind) that I can successfully deploy as follows (Host is Arch Linux)

    /opt/android-qt5/5.2.0/bin/qmake
    make install INSTALL_ROOT=android-build/
    /opt/android-qt5/5.2.0/bin/androiddeployqt --output android-build/

    Although the only permission is my AndroidManifest.xml is

    <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>

    but androiddeplyqt keeps adding

    <uses-permission android:name="android.permission.CAMERA" />
    <uses-permission android:name="android.permission.RECORD_AUDIO" />
    <uses-feature android:name="android.hardware.camera" />

    to the AndroidManifest.xml. Any way to prevent that behaviour?

    1 Reply Last reply
    0
    • frederikF Offline
      frederikF Offline
      frederik
      wrote on last edited by
      #2

      Do you have QT += multimedia in your .pro files somewhere? It will pull in this permission I guess. Also you could try to let Creator create the manifest file in the source dir (in deploy options) and then edit that version. If it doesn't work, file a bug at bugreports.qt-project.org

      1 Reply Last reply
      0
      • N Offline
        N Offline
        nikta
        wrote on last edited by
        #3

        I figure out the funny bug. In the AndroidManifest.xml I had

        <!-- %%INSERT_PERMISSIONS -->
        <!-- %%INSERT_FEATURES -->

        and it turns out to be the problem. After removing these lines the problem solved.

        1 Reply Last reply
        1

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved