Skip to content
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

[BUG] Not working in OSX Ventura 13.5.2 on M1 Pro #12

Open
gallacus opened this issue Sep 20, 2023 · 4 comments
Open

[BUG] Not working in OSX Ventura 13.5.2 on M1 Pro #12

gallacus opened this issue Sep 20, 2023 · 4 comments
Assignees
Labels
Reviewing Item is being reviewed

Comments

@gallacus
Copy link

Describe the bug
When I attempt to run ./RingSnapshotDownload, no matter what I do with permissions, it returns:
zsh: killed ./RingSnapshotDownload

To Reproduce
Steps to reproduce the behavior:

  1. Modify Settings.json to include RingUsername, RingPassword
  2. Open Terminal
  3. Change directory to directory where RingSnapshotDownload is
  4. run ./RingSnapshotDownload
  5. returns: zsh: killed ./RingSnapshotDownload

Expected behavior
Downloads image, or when using -list provides list of Ring devices

Screenshots
None

Versions (please complete the following information):

  • OS: Ventura 13.5.2 on M1 Pro chip
  • RingSnapshotDownload: osx-arm64
@gallacus gallacus added the Reviewing Item is being reviewed label Sep 20, 2023
@zmre
Copy link

zmre commented Oct 2, 2023

You might want to check your quarantine settings. Try xattr -d com.apple.quarantine RingSnapshotDownload and then run again. You might also need to check the System Preferences Security and Privacy settings as that page sometimes has a warning about running things downloaded from the internet and you may have a prompt there to "open anyway" or something like that.

@zmre
Copy link

zmre commented Oct 2, 2023

I take it back. I'm having the same problem even after removing the quarantine flag. System logs show: ASP: Security policy would not allow process: 555555, /Path/To/RingSNapshotDownload but I'm not getting a popup or seeing a way to run anyway. I'm guessing it needs to be signed. I think there's a way for me to just sign locally and I'll try that next.

@zmre
Copy link

zmre commented Oct 2, 2023

Yeah, running codesign on the binary fixed the issue, but you have to have a mac developer account and code signing cert. Hope this helps.

@amotivv
Copy link

amotivv commented Dec 30, 2023

You can also create a personal cert and give it code signing to get you going on Mac.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reviewing Item is being reviewed
Projects
None yet
Development

No branches or pull requests

4 participants