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

Nothing happens after last setup command #53

Closed
tonysprenk opened this issue Jul 11, 2023 · 10 comments
Closed

Nothing happens after last setup command #53

tonysprenk opened this issue Jul 11, 2023 · 10 comments
Labels
bug Something isn't working

Comments

@tonysprenk
Copy link

Describe the bug
I run ./iSponsorBlockTV --macos_install but after that nothing happens.

@tonysprenk tonysprenk added the bug Something isn't working label Jul 11, 2023
@oxixes
Copy link
Contributor

oxixes commented Jul 11, 2023

Could you be a bit more specific on the steps you performed? Did you follow the guide at https://github.com/dmunozv04/iSponsorBlockTV/wiki/Installation#macOS?

@tonysprenk
Copy link
Author

tonysprenk commented Jul 11, 2023

Yes I followed all the steps as described in the wiki but nothing happens after the last step.

@oxixes
Copy link
Contributor

oxixes commented Jul 11, 2023

Do you have an M1/M2 mac or an Intel mac?

@tonysprenk
Copy link
Author

M2

@oxixes
Copy link
Contributor

oxixes commented Jul 11, 2023

IIRC iSponsorBlockTV was compiled for Intel macs only (Rosetta may not be working correctly). Also, that version is outdated, so it would be better to run directly from source (or even better, setup docker). @dmunozv04 may have more information regarding this issue.

@dmunozv04
Copy link
Owner

Was the output of ./iSponsorBlockTV --macos_install blank or did it show the configurator?
Also please check if ~/Library/LaunchAgents/com.dmunozv04.iSponsorBlockTV.plist exists

@tonysprenk
Copy link
Author

It was blank. Building from source worked. The file is there but not sure if that’s from building from source.

@tonysprenk
Copy link
Author

If needed I can uninstall everything and do testing.

@dmunozv04
Copy link
Owner

If the launch daemon was there, it means that at least some part of the macOS install did work, but it failed at some point when loading the configurator for the first time

@dmunozv04
Copy link
Owner

This will be fixed by #108

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants