UPDATE: Finally, I confirm that Roland Cloud plugins NEED read access to the "~/Library/Application Support/Roland Cloud/shared" directory to check their permission status! The fact is that the beta version contained these (XCode injected?) additional entitlements: com.apple.security.temporary-exception.files.absolute-path.read-only/ com.apple.security.temporary-exception.mach-lookup.global-namecom.apple.testmanagerdcom.apple.dt.testmanagerd.runnercom.apple.coresymbolicationd That is :(

I actually said something stupid. Enabling com.apple.security.network.server works. It involved reinstalling some things. A thousand thanks!

Thank you Quinn! I've added the server entitlement but but that wasn't enough, Roland plugins need read access to the "~/Library/Application Support/Roland Cloud" directory to check their authorization status :( com.apple.security.temporary-exception.files.home-relative-path.read-only /Library/Application Support/Roland Cloud/ Now I hope this exception will be accepted by the review team. Bruno

Thank you Quinn :) Checking the notarization status: xcrun altool --notarization-info (notarization ID) --username "(username)" --password "password" I''ve got this error description in the returned log: "issues": [ { "severity": "error", "code": null, "path": "framework.pkg Contents/Payload/Library/Frameworks/framework.framework/Versions/A/framework", "message": "The signature does not include a secure timestamp.", "docUrl": null, "architecture": "x86_64" }, { "severity": "error", "code": null, "path": "framework.pkg Contents/Payload/Library/Frameworks/framework.framework/Versions/A/framework", "message": "The signature does not include a secure timestamp.", "docUrl": null, "architecture": "arm64" } ] Adding the --timestamp flag to XCode "other signing flags"solved the issue.

It seems that the issue was related to DTS mail failing to reach my mailbox. I sent a mail directly to macdstsupport which replied: "I did respond to your incident on January 13th at 5:34PM Pacific time.  You must have not received it?"

This problem is caused by an invalid (expired) certificate. You can work around the problem by temporarily changing the system date to before the certificate expiration date.

Thank you. The command line method will be the workaround 🙂 until somebody at Apple fixes this.