Post not yet marked as solved
FYI similar error here:
objc[8608]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libamsupport.dylib (0x21488b678) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1065ac2c8). One of the two will be used. Which one is undefined.
objc[8608]: Class AMSupportURLSession is implemented in both /usr/lib/libamsupport.dylib (0x21488b6c8) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1065ac318). One of the two will be used. Which one is undefined.
objc[8609]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libamsupport.dylib (0x21488b678) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1079c02c8). One of the two will be used. Which one is undefined.
objc[8609]: Class AMSupportURLSession is implemented in both /usr/lib/libamsupport.dylib (0x21488b6c8) and /Library/Apple/System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1079c0318). One of the two will be used. Which one is undefined.
Brand new MacBookPro M1, launched a few commands for the first time (git, python3) these errors pop up. Subsequent runs seem to be unaffected.
I am having the exact same situation: "You must first sign the relevant contracts online. (1048)", and I'm not even distributing my products (Adobe Photoshop add-ons) through Apple, so there's no way that I fill user info for Paid Apps.Moreover, the notarization process used to work flawlessly last week, I've changed nothing at all, and I've already agreed on XCode terms and conditions.My undestanding is that this is a very annoying, random error – it's been two days now that I can't notarize a dmg. In the past I've had similar strokes of bad luck, then some good luck, and so on.But again, it is annoying to say the least :-/
Post not yet marked as solved
Hi,while discussing with another developer, the following scenario came to our minds.Say that I have signed .a pkg and .app, wrapped in a notarized/stapled outer dmg, as we've discussed. What if the user downloads the .dmg and then disconnects from the internet? The notarization ticket is stapled to the dmg, hence it opens successfully... but being him/her offline, what about the .pkg and .app, will they run being signed only without online check for the dmg content? I.e. does Finder recognize that they come from a notarized container? And what if the user copies them from the .dmg to the HD... shouldn't they be individually notarized as well at this point?I am aware that we're talking really edge cases here, but it'd be nice to know in advance to streamline support calls :-)Thank you!Davide
Post not yet marked as solved
Very kind of you, thanks for confirming!Davide
Post not yet marked as solved
Hi Quinn,very similar situation here – I develop Photoshop panels (which are basically web applications, that may or may not include actual Photoshop plugins written in C++).I am building an installer.pkg via Packages (by WhiteBox) in charge of the actual files deployment, that in turn is wrapped with a product.dmg that gathers: the installer.pkg, plus an uninstaller.app (an app-ified AppleScript) plus some .pdf documentation. The .dmg is what the user downloads (from my own store).A couple of questions:Could you please confirm that the outer .dmg is the only one in need to be notarized?Besides notarization, at the moment, I'm signing them all: the .pkg, the uninstaller.app and the .dmg – is this a good practice or redundant?Thank you very much!Davide Barranca
