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

Neither installer nor tar ball methods for install working. Plugin fails on OBS launch. #1290

Open
jtroussard opened this issue Jan 4, 2025 · 6 comments

Comments

@jtroussard
Copy link

jtroussard commented Jan 4, 2025

Operating System Info

Sonoma 14.5

OBS Studio Version

31.0.0

Advanced Scene Switcher Version

1.28.1

Plugin settings

No response

OBS Studio Log URL

https://obsproject.com/logs/CMh4BLFF6VCTMmjD

OBS Studio Crash Log URL

No response

Expected Behavior

For OBS to open without error. For OBS to recognize the plugin.

Current Behavior

OBS Crash Log (Abbreviated)
Process: OBS
Version: 31.0.0 (12207818817)
OS: macOS 14.5 (23F79)
Code Type: ARM-64 (Native)
System Integrity Protection: Enabled
Exception Type: EXC_BAD_ACCESS (SIGKILL - Code Signature Invalid)
Termination Reason: Namespace CODESIGNING, Code 2 Invalid Page

System Specifications
Model: Mac14,3
Uptime Since Boot: 280,000 seconds
Time Since Wake: 9,253 seconds
Plugin Failure
Plugin: advanced-scene-switcher

Path: /Users/USER/Library/Application Support/obs-studio/*/advanced-scene-switcher.plugin/Contents/MacOS/advanced-scene-switcher
Library: advanced-scene-switcher-lib.so
Error: Invalid Code Signature
Error Location (dyld):

dyld3::MachOFile::isMachO
Mapped File: Address 0x161054000
Additional Details: The crash appears related to code signing validation of the advanced-scene-switcher plugin, as reported in the dyld mapping process. Removing or updating this plugin may resolve the issue.

Steps to Reproduce

  1. unable to install via mac installer (generic error "Failed to install" no further details)
  2. download and unpacked tar ball
  3. copied contents into the obs plugin directory ~/Library/Application\ Support/obs-studio/plugins/
  4. launch OBS

Anything else we should know?

Mac mini M2 Chip OS Sonoma v14.5

@jtroussard jtroussard changed the title Neither installer or tar ball methods for install working. Plugin fails on OBS launch. Neither installer nor tar ball methods for install working. Plugin fails on OBS launch. Jan 4, 2025
@WarmUpTill
Copy link
Owner

Please try running the following command in the terminal application:
codesign --force --deep --sign - ~/Library/Application\ Support/obs-studio/plugins/advanced-scene-switcher.plugin

@heathdutton
Copy link

heathdutton commented Jan 13, 2025

I am having the same problem with MacOS Sequoia 15.2, OBS 31.0, plugin version 1.28.1.
I tried your solution @WarmUpTill but it does not seem to solve it:

codesign --force --deep --sign - ~/Library/Application\ Support/obs-studio/plugins/advanced-scene-switcher.plugin

But when attempting to open OBS, I still get the notice:

Apple could not verify “advanced-scene-switcher.plugin” is free of malware that may harm your Mac or compromise your privacy.

Note, I'm using the universal tarball. The notice shows twice if I click Done.

@WarmUpTill
Copy link
Owner

@heathdutton I think what you are mentioning here is a different type of problem.
Please try holding down Control and click on the OBS.app, then select “Open” from the context menu.

@jtroussard
Copy link
Author

@WarmUpTill I should have some time this evening to give this solution a try. Thanks for the feedback.

@WarmUpTill
Copy link
Owner

@jtroussard sorry the previous comment was only referring to the other type of issue reported by heathdutton.
For your problem I am unfortunately at a bit of a loss.
The only idea I would have is to completely remove the ~/Library/Application\ Support/obs-studio/plugins/advanced-scene-switcher.plugin directory and then try to reinstall it again.

@heathdutton
Copy link

Perhaps you are right and this is a different issue?

One solution was to find it in Privacy & Security, click "Allow Anyway" and one last time use admin credentials. I didn't have to do this till after the Sequoia update.

Image

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

No branches or pull requests

3 participants