issue still exists in final Xcode 15

same issue here, no more notarisation possible on Xcode 14.2 (on macOS 12.6.7). i cannot confirm that it works after 4-5 times, had 10 failures in a row with the very same "Couldn’t communicate with a helper application." message.

same here and for any other Xcode user. the lack of quality control at Apple is unbelievable

we are seeing SMAppService.mainAppService.status returning SMAppServiceStatusNotFound for some of our users. from the documentation: SMAppServiceStatusNotFound = An error occurred and the framework couldn’t find this service. however shouldn't it be impossible for the mainAppService to be not found? it seems that return would only make sense for agents/daemons/loginitems. any idea what is going on here?

no idea until Apple says anything about this. i've filed a bug report about the missing documentation on this  FB8901281 'LSMinimumSystemVersionByArchitecture' undefined for "Apple Silicon"

i am constantly seeing this with pretty much any built-in app in Big Sur beta1 and 2. its impossible to launch TextEdit, crashes with this message any time SpeedTracer Error NSURLConnection to https://speedtracer.apple.com/tracer/analyze failed with error: A server with the specified hostname could not be found.

we've successfully created native code to parse the Timestamp from the binary. this is a few orders of magnitude faster than calling codesign (which also insists on returning localized date formats which is just *insanity* for parsing programatically). the Timestamp is just yyyyMMddHHmmssZ0 somewhere at the end of the binary.now we'd like to parse the 'Signed Time' (kSecCodeInfoTime) directly too (especially because this is often not even returned by 'codesign' unless you point it at some embedded framework on pre-Catalina systems!), but we didn't make headways there. it certainly doesn't seem to be stored in 'yyyyMMddHHmmss' format in the main executable.mighty and wise eskimo, do you have any technical information here?

fully agree. but everything that has changed since 10.6 is designed to make developers miserable.

we are also seeing this on macOS (Catalina) now, but tests have revealed that despite this message the actual saving and reading of the preferences still works fine. we've tested up to one million keys with a combined size of 30 MB. many error messages but the actual operations worked just fine.Apple, whats the plan here?