barijaona / UniversalMailer

Universal Mailer plugin for Mail.app
https://github.com/barijaona/UniversalMailer
GNU General Public License v3.0
27 stars 3 forks source link

Not working under macOS 13.3 #10

Closed jabeler closed 1 year ago

jabeler commented 1 year ago

Describe the bug Running the installer after updating to macOS 13.3 results in the 'unsupported plugin' message.

To Reproduce

  1. Updated to macOS 13.3
  2. Run the installer
  3. Attempt to enable the plugin

Screenshots

Screenshot 2023-03-27 at 1 02 46 PM

Please complete the following information:

unsureone commented 1 year ago

I can confirm this. For macOS 13.3, the Supported13.3PluginCompatibilityUUIDs needs to be updated in UniversalMailer's "Info.plist" file to read: 281F8A5C-0AF9-4BE6-8B8A-C0CB9C2068BE

We can't do this ourselves anymore, because macOS Ventura requires that the app be code signed again by the developer if any changes are made (including changing a string in "Info.plist").

-- David

dfelicia commented 1 year ago

Bummer. I would have held off on upgrading to 13.3 had I known it'd break UniversalMailer. :-(

jonathanlaniado commented 1 year ago

+1, @barijaona, is this something you think you could look into fixing? 😊

jaedon commented 1 year ago

If you have access to Xcode, you can follow these steps to temporarily resolve the issue:

Clone the UniversalMailer repository from @barijaona's GitHub account using the following command: git clone git@github.com:barijaona/UniversalMailer.git -b v/3.0.7

Open the Scripts/fix_info.plist.sh and edit the entry Supported13.3PluginCompatibilityUUIDs and below to '281F8A5C-0AF9-4BE6-8B8A-C0CB9C2068BE'.

Replace the existing UniversalMailer.mailbundle file in /Library/Mail/Bundles/ with your own build.

Use the spctl command with administrative privileges to add a Gatekeeper rule to the updated mailbundle with the following command: sudo spctl --add /Library/Mail/Bundles/UniversalMailer.mailbundle

Note that you do not need to be a member of the Apple Developer Program to perform these steps.

dfelicia commented 1 year ago

If you have access to Xcode, you can follow these steps to temporarily resolve the issue:

Clone the UniversalMailer repository from @barijaona's GitHub account using the following command: git clone git@github.com:barijaona/UniversalMailer.git -b v/3.0.7

Open the Scripts/fix_info.plist.sh and edit the entry Supported13.3PluginCompatibilityUUIDs and below to '281F8A5C-0AF9-4BE6-8B8A-C0CB9C2068BE'.

Replace the existing UniversalMailer.mailbundle file in /Library/Mail/Bundles/ with your own build.

Use the spctl command with administrative privileges to add a Gatekeeper rule to the updated mailbundle with the following command: sudo spctl --add /Library/Mail/Bundles/UniversalMailer.mailbundle

Note that you do not need to be a member of the Apple Developer Program to perform these steps.

Thank you very much for this! Worked like a charm. For others' benefit, the build output ends up in ~/Library/Developer/Xcode/DerivedData/UniversalMailer-bjortumwvyfkmoacmpvapupwxmnb/Build/Products/Debug

jonathanlaniado commented 1 year ago

Thank you @barijaona! https://github.com/barijaona/UniversalMailer/releases/tag/v/3.0.8

jabeler commented 1 year ago

You are a legend @barijaona. 🙌

AlexanderWillner commented 1 year ago

If you have access to Xcode, you can follow these steps to temporarily resolve the issue:

sounds like something that could be automated to fix the bundle after an OS update…maybe a daemon that could be added using the installer…