Skip to content

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

Open
contextnerror opened this issue Feb 9, 2025 · 10 comments
Open

Update failed on 10.14, now listed as "incompatible plug-in" #211

contextnerror opened this issue Feb 9, 2025 · 10 comments
Assignees
Labels
bug Something isn't working

Comments

@contextnerror
Copy link

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:

Incompatible Plug-ins Disabled
Mail has disabled the following plug-ins:

	MailTrackerBlocker.mailbundle

Contact the makers of these plug-ins for versions that are compatible with Mail 12.4.

To Reproduce
Steps to reproduce the behavior:

  1. Be presented with a new update. Choose to update.
  2. Click through the update (default install location, etc.)
  3. Be presented with a ⚠️ symbol and told the update has failed
  4. Try to re-enable plugin from preferences, be presented with incompatible message

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):

  • OS: 10.14.6
  • MailTrackerBlocker version: 0.8.7, I assume? I don't know if the update actually went through.
  • Other enabled plugins/extensions: none

Additional context
None I can think of right now.

@contextnerror contextnerror added the bug Something isn't working label Feb 9, 2025
@apparition47
Copy link
Owner

apparition47 commented Feb 9, 2025

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

@apparition47
Copy link
Owner

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 DataVaults directory? Instructions here: https://c-command.com/spamsieve/help/resetting-mail-s-privat

@contextnerror
Copy link
Author

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.

@apparition47
Copy link
Owner

Does the previous version 0.8.6 work for you?

@apparition47
Copy link
Owner

how to check the version number.

Image

@apparition47
Copy link
Owner

Just as a sanity check, could you also provide me the output of this:

defaults read /System/Applications/Mail.app/Contents/Info.plist PluginCompatibilityUUID

@contextnerror
Copy link
Author

I have yet to test the things from your previous comments, but here is the output:

2025-02-09 17:18:52.496 defaults[1229:41112] 
The domain/default pair of (/System/Applications/Mail.app/Contents/Info.plist, PluginCompatibilityUUID) does not exist

@contextnerror
Copy link
Author

Just reinstalled 0.8.6 and it works fine.

@apparition47
Copy link
Owner

apparition47 commented Feb 10, 2025

That's weird, how about this:

defaults read /Applications/Mail.app/Contents/Info.plist PluginCompatibilityUUID

In the meanwhile, I'll rollback this release

@contextnerror
Copy link
Author

A4343FAF-AE18-40D0-8A16-DFAE481AF9C1

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

2 participants