-
-
Notifications
You must be signed in to change notification settings - Fork 24
Update failed on 10.14, now listed as "incompatible plug-in" #211
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
Comments
Must be because of the change in the build env (GitHub Actions doesn't have macOS 12 runners anymore). Will have to roll back this release temporarily |
I tested on a macOS 12.6 VM and it worked so maybe that isn't the issue. Were you on 0.8.6 previously? Could you try resetting your |
It looks like it worked at first, I got to step 7 and was able to re-enable the plugin successfully. But as soon as I turned SIP back on and restarted I got the incompatible plugin error. I'm assuming I was on 0.8.6 previously as I have installed all updates I was presented with, but I don't actually know how to check the version number. |
Does the previous version 0.8.6 work for you? |
Just as a sanity check, could you also provide me the output of this:
|
I have yet to test the things from your previous comments, but here is the output:
|
Just reinstalled 0.8.6 and it works fine. |
That's weird, how about this:
In the meanwhile, I'll rollback this release |
|
Describe the bug
I was given a notification that there was an update for MailTrackerBlocker. I chose to update and clicked through the process as normal.
At the last step, I was told that the update had failed. Now when trying to re-enable the plugin I am presented with this message:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expected the update to complete successfully and continue operation, as it has done several times in the past.
Logs
I don't think I have any logs, but let me know if there's somewhere I should look for them.
Environment (please complete the following information):
Additional context
None I can think of right now.
The text was updated successfully, but these errors were encountered: