-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
[MAC] Cannot open a directory from within the Application #326
Comments
I confirm the bug. A fix is coming... |
Give these a try to see if they fix your issues. macOS amd64: macOS arm64: |
Thank you. I can confirm the second link fixes the issue, but it keeps crashing a bit. The first link crashes while opening. |
Can you post out the crashing logs that macOS generates when it crashes? |
Sure. This the log for amd64 - https://pastebin.com/uvMk0fSs Surprisingly I hvaen't been able to replicate a crash in the arm64 version. When I do I'll paste the logs here |
Here should be a fixed version of amd64: https://mega.nz/file/DCwxXZjK#JXSiqz2d4UlvdZ5ZjYoUfgBpgQmxKm7UL1sZHtZYBrA However, since you are on arm64 machine, you probably should keep using that one, except for the OTIO bug reported on #238. |
This is pretty embarrassing - I am very new to Mac and I didn't know the amd version wouldn't work on my arm machine :D. I will keep using this version that you shared. Looking forward to the updates !! |
Actually, the amd64 version can run on arm64 (M1, M2, M3,etc.) machines. It will run under an emulator called Rossetta2. That means it should run a tad slower, but it will work. The reason it was not working before was that it was missing a library that was installed on my machine but not on yours. Please give it a try to see that it actually boots. |
Hi I can say that the amd64 version doesn't boot. it defaults to crash every time I open it. I can check it with the specific library that you mentioned - can you point me where to install it? |
It cannot tell you what library is the problem without a crash log. First, try this version and see if it crashes: .amd64: If it still crashes, send me the crash log. I think then a new security feature of macOS that was updated in the New Year might be the problem. |
Happy to say that this version doesn't crash, and I can open directories without the error message popping. |
I'm on MacOS Sequoia 15.1.1.
When I select 'Open Directory' from the menu I always get an error saying 'ERROR: [FILENAME] does not exist or does not have read permissions'
Attaching a Screenshot -
I get the same error when I try dropping in a folder.
I can open a single image (drag and drop as well) but the issue seems to be only with trying to open directories.
I have used gatekeeper to unlock the app, and I've also given full disk access.
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: