I had the same issue. Notarization suddenly stopped working and I got a "package invalid" response.I enabled "Hardened Runtime" in my targets to resolve it.

I had the same issue and resolved it by addingsleep 0.5at the beginning of my upload DSYMs script phase.It seems that the dSYM path couldn't be resolved when the upload command runs too early.Depending on how fast your Mac is you may need to sleep a little longer.Edit: This was working fine on my iMac, unfortunately it still doesn't work on my Macbook Air even after increasing to 3 seconds :/

@Etresoft I didn't say that I'm notarizing a single static library or a Framework by itself ^^ I notarize my Framework as package, the package contains a binary and multiple libraries including the static library. Please note that I mentioned in my question that notarization does already work correctly for me when I build non-fat files. Only in case of fat files it fails. So I'm indeed able to notarize this archive.

Excellent! Problem solved. Sorry, I will try to clarify: I am able to notarize my installer package when the static library is a non-fat file (only one arch). But it still fails when I try to notarize it with the static library as fat file (universal). :)

@eskimo: Yes I'm building an SDK. I don't expect my clients to include the static lib but I want to offer it as an option. So I'm shipping both the dynamic and the static library. In the past I only shipped the dynamic library but we got requests from some Linux customers to include a static version too, so I added it on Linux and thought it wouldn't hurt when I add it on macOS too. Can you please tell me more about those workarounds :) Thanks

I'm also seeing these crashes in Crashlytics. Only iOS 17 Beta users are affected. I was unable to reproduce this issue.