-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
macOS file dialog permission loop #475
Comments
Same issue here. Also M1 Mac. |
Confirmed on my M1. |
Qt bug report: https://bugreports.qt.io/browse/QTBUG-99894 |
Ok, since this issue is so unacceptable I made an alteration to this release. There is now a separate Intel and arm64 download. You can get the arm version here: https://github.com/jurplel/qView/releases/download/5.0/qView-5.0-arm64.dmg |
Scratch that. I ran into an issue with the arm64 dmg and found that it wouldn't open without running I then thought, what if the original issue was caused by the same lack of signature? Sure enough, signing the universal binary fixed the issue! |
I will wait for confirmation from someone else before I close the issue. |
You have to right click and press open to pass that. Notarizing apps properly requires a developer account :( |
yeah, I'm used to that. but in this case it was coming back every time I opened it. BUT . . . now it seems okay . . . yeah. seems to be working now. |
hooray |
I can't figure out where to get the latest macos build. I don't see a 5.0.1, and the nightly is from Friday. |
I just replaced the 5.0 dmg |
Environment:
Information:
File dialog asks for access permission to use folders repeatedly:
Didn't notice/hard to debug because it doesn't show up when compiling in qt creator.
Not sure if M1 specific: Running with Rosetta 2 does not fix it.
Qt 5.15.2 build works fine, only qt 6.2.2 build is affected.
Giving full disk access explicitly does not fix the issue.
Sometimes I open qView and the issue just doesn't happen?
This may go the way of the QTBUG before long
After testing x86_64, arm64, and universal builds with 6.2.2 locally, I can confirm that only universal builds seem to be affected by this issue.
Would be interested to know if this happens on Intel machines as well
The text was updated successfully, but these errors were encountered: