-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
ProcessException: Permission denied on MacOS Sonoma 14.1.1 macos app #372
Comments
I'm using MacOS Sonoma 14.1.1 M1 chip |
|
You don't need to add permissions to the whole project. I just experimented with it. I just need to add x permissions to the engine. |
Its still not working for me. Do you need to have admin acces on your mac device's user account? Because my user is not an administrator |
@farellsujanto Is your project directory and running directory in your user directory? If not, then this is a matter of strict authority. You can either use the administrator account to authorize x permissions or run under your user directory. |
I think my problem is, I don't know which prisma-query-engine is called on the app, because when I delete all prisma-query-engine from the project directory it still says Permission denied but there is no any of the engine remaining. Is it possible to specify which prisma-query-engine location to be used on the app? |
@farellsujanto $PWD Engine files should exist in these three locations, otherwise an error of not finding the engine will be thrown instead of a permission error. |
I've found something strange, my project location is at When I tried to delete it it shows another error
Then I restore the deleted prisma-query-engine and add chmod +x to it, but it gives me another error
Just like what is reported on #326, I think its better if we have some freedom to use which prisma-query-engine that we wanted to use. |
@farellsujanto The temporary solution is usually:
Notes: I'm working on the macOS integration of Flutter and orm normally, and I can directly rely on |
In addition, the root cause of this problem is that the engine is included in the app's data directory. Due to macOS's permission control, the commands in it cannot be run directly from the outside. You can put the binary engine into flutter assets and write it to the system temporary directory during the startup phase, and then run it. |
Yeah I confirmed this is because of I've also found out that you don't need to use the temporary solution that you gave above by removing the app sandboxing on XCode. I don't know yet the side effect of removing the sandboxing but it works fine without any changes on the code. |
I'm developing windows & macos app, the windows one is already running well, but I got some problem when building the macos app. Already doing chmod +x & 777 on the entire project & builds but still not working.
I'm using
orm v4.1.0
I got this error
Here is the flutter doctor result
On release build its forced close but in debug build I got those error log, can you help me to solve this? Thanks!
The text was updated successfully, but these errors were encountered: