Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Return empty getExistingDirectory for Android SDK >= 30
QtWS25 Last Chance

Return empty getExistingDirectory for Android SDK >= 30

Scheduled Pinned Locked Moved Solved Mobile and Embedded
android 11file managementqfiledialog
4 Posts 2 Posters 464 Views
  • 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.
  • K Offline
    K Offline
    Kafabih
    wrote on 18 Dec 2022, 03:33 last edited by Kafabih
    #1

    Hello everyone, I have problem with QFileDialog::getExistingDirectory is returned empty value. I used QT 6.2.4 which tested on Android 13 (SDK 33) and may be affected on Android 11 & 12 which is using MANAGE_EXTERNALS_STORAGE permission. Is anyone tried another way to facing this problem?

    1 Reply Last reply
    0
    • K Offline
      K Offline
      Kafabih
      wrote on 18 Dec 2022, 04:28 last edited by
      #2

      I reported this bug here -> Return empty values getExistingDirectory

      1 Reply Last reply
      0
      • K Offline
        K Offline
        Kafabih
        wrote on 30 Dec 2022, 06:00 last edited by Kafabih
        #3

        Alrigh I found alternative way to facing this problem by using QFileDialog::getOpenFileUrl.

        M 1 Reply Last reply 30 Dec 2022, 19:03
        0
        • K Kafabih
          30 Dec 2022, 06:00

          Alrigh I found alternative way to facing this problem by using QFileDialog::getOpenFileUrl.

          M Offline
          M Offline
          mvuori
          wrote on 30 Dec 2022, 19:03 last edited by
          #4

          In the bug report you write that
          "have to edit what I reported here before is wrong method. So the right method is getOpenFileNames. I am apologized."

          Of course, you should have updated your post here.

          More often than not, a problem is not in the API, but new conditions (such as new OS version) that expose a problem in how you use it. And you don't tell anything about it.

          1 Reply Last reply
          0

          • Login

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