4.4.2 multiple requests for access to download folder

[BrahamUK]

qBittorrent & operating system versions

4.4.2
MacOS Monterey 12.3
Macbook pro 14 inch 2021
Cip Apple M1 pro

What is the problem?

Qbt makes multiple and repeated request for access to the downloads folder, both on startup and thereafter.
System privacy preferences show that Qbt already has access

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

No response

[kopaka7]

I am getting 5 requests for access to the downloads folder every time I open the app, here are the screenshots of the message and the privacy settings for Qbittorrent. This started with 4.4.2.

[ghost]

Do you have any torrents in the Downloads folder?

[BrahamUK]

Yup.

[ghost]

This is probably a Qt6 bug.
https://forum.qt.io/topic/133116/qt-creator-6-on-macos-big-sur-keeps-asking-for-access-to-documents

https://serveanswer.com/questions/qt-creator-6-2-2-repeatedly-asking-for-folder-permission-full-disk-access-enabled

[Yepyep911]

I am having the same problem as the OP on a MBP 2021 Pro.

[srvrguy]

For this permissions popup issue, you can try one of the workarounds found at https://bugreports.qt.io/browse/QTCREATORBUG-26705#comment-646292.

I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

[ghost]

One of the comments mentioned
“Happens for unsigned, fat (intel+arm) binaries, on arm machines (tccd/Security framework throws internal error)”

@sledgehammer999 seems like the solution is to sign the app or create separate binaries.

[recoi1er]

just updated, same issue as well. except its a lot more than 5 times for me.

[Yepyep911]

I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

Thank you very much! This worked a charm for me.

[banksxs]

I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

Thank you very much! This worked a charm for me.

Terminal says 'no such file or directory' when I typed this

[Yepyep911]

I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

Thank you very much! This worked a charm for me.

Terminal says 'no such file or directory' when I typed this

You'll want to type "codesign -s - --deep " into Terminal and then act like you're dragging the qBittorrent app from your Applications folder (or wherever you keep that app) into the spot after "deep " so it gets the exact path to that app. On my machine it looks like this: "codesign -s - --deep /Applications/qbittorrent.app" without the quotation marks, of course.

[vlade11115]

For this permissions popup issue, you can try one of the workarounds found at https://bugreports.qt.io/browse/QTCREATORBUG-26705#comment-646292.

I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

It worked for me, thank you.
codesign -s - --deep /Applications/qbittorrent.app is command that I used.

[jake1945]

codesign -s - --deep /Applications/qbittorrent.app worked for me after I restarted the application twice. Thanks for all your help.

[vvzvlad]

Confirmed the bug, MacBook Pro (14-inch, 2021), MacOS 12.3.
codesign solved the problem.

[FuturePilot]

I can also confirm the codesign command has solved the problem.

[jegillikin]

Another confirmation for the success of the codesign method, macOS 12.2 on Mac mini (M1, 2020).

[antonio59]

codesign command solved this annoying popup.

[harshadpawale]

Confirmation that the codesign method solved the issue on M1 Macbook Pro 2021 base model.

[qwertyasdfasdfqwerty]

The codesign command seems to prevent the access prompt from appearing more than once, but once it is accepted, the program becomes unresponsive and sometimes freezes the entire system.

[recoi1er]

Still ongoing and the workaround doesn’t work anymore. Have ran it multiple times over the last few weeks and after a random time it will just start happening again.

[abrn]

The codesign trick worked for me but after a while (as mentioned above), the prompts are appearing again. The app will freeze or crash at random times too - 2021 M1 Macbook Air (Monterey 12.4). Allowing the app full disk access doesn't change anything either. This only started happening after I updated to the latest qbit version.

The issue is much worse when saving files to a removable volume. The prompt appears repeatedly the whole time the content is downloading.

[isbasex]

For this permissions popup issue, you can try one of the workarounds found at https://bugreports.qt.io/browse/QTCREATORBUG-26705#comment-646292.

I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

cd /Applications
codesign -s - --deep qBittorrent.app

it works

[qwertyasdfasdfqwerty]

For me the problem was the installed search plugins, I deleted them and the redundant allow access messages gone.

Would you be so kind as to share how to do this? I'm willing to try whatever, and it's unfortunate the Mac release of this is given so little attention.

[ishridharhegde]

For this permissions popup issue, you can try one of the workarounds found at https://bugreports.qt.io/browse/QTCREATORBUG-26705#comment-646292.

I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

This works.
As other have suggested, point to the path of the app.
codesign -s - --deep /Applications/qbittorrent.app

[lucein1774]

For this permissions popup issue, you can try one of the workarounds found at https://bugreports.qt.io/browse/QTCREATORBUG-26705#comment-646292.
I personally tried the ad-hoc codesign method (item 5 in the list on that bug), and after one single prompt when I re-launched the application it stopped. The command I specifically used was codesign -s - --deep qBittorrent.app. You shouldn't need to be part of the Apple Developer program to use that command.

This works. As other have suggested, point to the path of the app. codesign -s - --deep /Applications/qbittorrent.app

Hi I tried this, but still get the popup whenever a file is accessed. I even went so far a s clearing out the app of all torrents. doing the codesign, relaunching and adding the torrent files back to the app. but still got the popup when the files started rechecking. Then again when files started to download again after the check

[fjsdljfdlksdjf]

This software is just complete dog 💩 on macOS. This development community is pathetic that it can't get its s*it together for a platform as big as macOS. Because of endless frustration with this software I eventually switched to Transmission months ago.

[alexandrucancescu]

I've had the same problem for the past year. I get 8 requests to grant access to the "Downloads" folder whenever I open the app.

[Shakahs]

qBittorrent is unusable on MacOS until this is fixed. I had to switch to Transmission.

[qwertyasdfasdfqwerty]

Yup, the last six months of comments sums it up succinctly. This renders the application unusable on a Mac. It's a hassle to migrate a thousand torrents to a new client (or at least it was the last time i looked into it), so my 'solution' has been to stay on 4.3.9.

I don't want to be using outdated software for much longer, so if this issue continues to be neglected as it has been, it'll be finally time to jump ship. Which is a shame.

Is there ANYTHING that we can provide as M1 Mac users to assist in finally resolving this issue?

[glassez]

Is there ANYTHING that we can provide as M1 Mac users to assist in finally resolving this issue?

M1 Mac for testing/debugging.

[glassez]

my 'solution' has been to stay on 4.3.9.

Have you tried one of the latest qBittorrent versions built with libtorrent-1.2?

[jake1945]

vlade11115 <https://github.com/vlade11115> commented on Mar 30, 2022 <#16728 (comment)> I used the solution posted at this time and it worked. I have a M1 MacMini

…

On Feb 19, 2023, at 19:26, qwertyasdfasdfqwerty ***@***.***> wrote: Yup, the last six months of comments sums it up succinctly. This renders the application unusable on a Mac. It's a hassle to migrate a thousand torrents to a new client (or at least it was the last time i looked into it), so my 'solution' has been to stay on 4.3.9. I don't want to be using outdated software for much longer, so if this issue continues to be neglected as it has been, it'll be finally time to jump ship. Which is a shame. Is there ANYTHING that we can provide as M1 Mac users to assist in finally resolving this issue? — Reply to this email directly, view it on GitHub <#16728 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYPFIE4IHHXNWBCYRGECEBTWYLP6TANCNFSM5RUALYHA>. You are receiving this because you commented.

[srvrguy]

The codesign method I posted above still works for me on an M1 Mac mini (and also worked on my older Intel iMac). It's worth noting that if you upgrade the application, you need to run the command again on the new version.

[jake1945]

I’ve not had to do this, Michael.

…

On Feb 20, 2023, at 10:03, Michael Johnson ***@***.***> wrote: The codesign method I posted above still works for me on an M1 Mac mini (and also worked on my older Intel iMac). It's worth noting that if you upgrade the application, you need to run the command again on the new version. — Reply to this email directly, view it on GitHub <#16728 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYPFIE3NM5XAWHMFW45JKW3WYOWWJANCNFSM5RUALYHA>. You are receiving this because you commented.

[sledgehammer999]

so my 'solution' has been to stay on 4.3.9

IIRC that version includes only x64 binaries (intel). Newer versions include both x64 and arm64. From my understanding, Apple is more stringest in enforcing policies on arm64 binaries. When you launch the newer qbt version on an arm64 Mac the OS automatically chooses the arm64 binaries. I am not sure if there is a way to tell it to launch the x64 version instead.

I wonder if I ad-hoc sign the releases and distribute them, will it work?

[sledgehammer999]

I have just released v4.5.1 for macOS which I also signed using a self-signed certificate. I hope that at least now the folder permissions will stick between re-launches of the application.

[BrahamUK]

v4.5.1 for macOS has resolved this issue for me. Many thanks!

[FuturePilot]

So far so good with 4.5.1. I only got the popup once when I first launched it after updating.

[lucein1774]

the 4.5.1 for me so far is more stable than before. I am not getting the storage popup requests as before, which is step in the right direction. Thank you @sledgehammer999 !

So far I havent had to remove all the Fastresume files after trying to reopen the app.
I did have an issue where the app after closing still showed in the Activity monitor and Force quit dialogs. Showing the app as not responding. So I had to force quit the app to stop it.

[sledgehammer999]

This seems probably fixed. So I am closing it.