Skip to content

NoSQL Workbench - “DDBLocalStart” can’t be opened because (null) is not allowed to open documents in Terminal.

4

When I try to run DynamoDB Local using the latest version (3.4.0) of the NoSQL Workbench on my M1 Mac, I get an error:

“DDBLocalStart” can’t be opened because (null) is not allowed to open documents in Terminal.

It looks like the NoSQL Workbench is trying to shell commands out to start DynamoDB Local?

Enter image description here

Stopping the local server doesn't work with a similar error.

The product feedback sends me to the old forums, which redirect to here...

asked 3 years ago1.3K views
3 Answers
1

I faced the same issue on MacOS Ventura with NoSQL Workbench: Version 3.4.0 (3.4.0). I couldn't find a way to allow the app to open the script in the default Terminal. I found a work around though, if you use iTerm, you can set that as your default to open scripts. Hope that helps!

The location of ddb local scripts Set iterm as default

answered 3 years ago
0

Thanks! I doubted it was the problem though, since I code in Neovim in the MacOS Terminal all day. :)

But, I checked, and Terminal already has access to all the directories. I also giving the Terminal full disk access and that didn't work either. Doing the same with NoSQL Workbench didn't make any difference either.

From an app design point of view, shelling out commands doesn't sound like the ideal way to do things.

answered 3 years ago
-1

You may need to grant Terminal permission to access Documents in System Preferences > Security & Privacy > Files and Folders. Alternatively, you can give Terminal Full Disk Access in the same pref pane. DynamoDB Local is .jar file and NoSQL Workbench starts it by invoking a shell command.

AWS
answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.