I think I've missed the opportunity to make a useful experiment, as notarytool seems to be consistently working now even with the original command line. My thanks to whoever at Apple fixed this!

I'd be happy to try key-based authentication, but I don't think I know how. I'm not sure I understand the documentation. What should the command options look like for that?

I've been getting this error intermittently for several days, but today it seems to be happening 100% of attempts. Feedback filled: FB17763219 Bob

Was there ever a solution to this? I'm facing the same problem with some custom hardware.

Whatever was causing this seems to be fixed starting about or before 11:40 PM March 2023. I've had several successful runs since then.

I'm seeing this error 100% of the time since yesterday (9:05PM Eastern Daylight time March 6).

I have the same issue. A .app that starts with a script in Contents/MacOS. Works fine on an Intel Mac or an M1 machine with Rosetta 2 installed. Does not work on an M1 Mac without Rosetta 2. % open -a DecoderPro.app The application /Applications/JMRI/DecoderPro.app cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10826 "kLSNoLaunchPermissionErr: User doesn't have permission to launch the app (managed networks)" UserInfo={_LSFunction=_LSLaunchWithRunningboard, _LSLine=2436, NSUnderlyingError=0x13d711060 {Error Domain=RBSRequestErrorDomain Code=5 "Launch failed." UserInfo={NSLocalizedFailureReason=Launch failed., NSUnderlyingError=0x13d711870 {Error Domain=NSPOSIXErrorDomain Code=111 "Unknown error: 111" UserInfo={NSLocalizedDescription=Launchd job spawn failed with error: 111}}}}} Starting the script works:% open DecoderPro.app/Contents/MacOS/StartJMRI  with no extra messages. Somehow, starting on M1-only is doing something different from starting with M1-plus-Rosetta-2