Once again, thanks to Xojo to the feature that lets sign (notarise) Mac apps. I was able to do it with the help of this community (thanks to everyone).
A few months ago, I encountered a Xojo error while building/signing my applications. I missed the email from Apple that I had to sign the new agreement (like all of us, I receive to many emails), I searched what was wrong during a long time. I just received the same email and luckily I didn’t miss it, so I signed it right away.
Is there a way the Xojo error message more explicit, or @Alyssa_Foley post an Announcements that Apple agreement have been updating and we have to sign them?
AFAIK… no way to know that the error is because there is a pending license agreement (moreover what is reported in the log created during the process from the Xojo IDE).
I know that, sometimes, the email from Apple can go through the Inbox without noticing it… but it is worthwhile to think about this as the first culprit when some of the signing / notarising / Publishing processes go wrong.
Yeah, for processes as Notarization or Publishing to the Mac App Store (App Store Connect), the IDE creates a Log file… and even displays a message box with information about the particular error.
In my experience with these (or even using Transport), I’ve found that most of the times the message returned by the Apple Service doesn’t points to the root (real) cause of it… as for example “Transporter wasn’t able to decompress the .pkg file” when the real issue is that a required entitlement is missing.
Thank you for yours answers, I will try to not miss the Apple emailing, and if I have problem signing my apps, I will try to think first to check my agreement.
I generally assume whenever notarization fails it’s because there’s a new agreement. It’s either that or my developer account has expired, and it’s on auto-renew so that’s probably not it.
