So we have been creating and distributing apps with the new notarization method for months now since Apple forced this extra step with Catalina. For months we have had no issues codesigning and notarizing our apps. At the beginning of this week all of the sudden when we try to notarize our apps we get this error message:"The executable does not have the hardened runtime enabled."In our Xcode project we do have hardened runtime enabled as well as Apple events and both have worked without a hitch. All of the sudden this week now we get that error above. So I thought I found a solution by adding the option in the codesignature like so :sudo codesign --force --deep --options runtime --sign "Developer ID Application: MYID" "MYAPP.app"This finally worked and allowed the app to be notarized succesfully. We thought we were in the clear. Then our customers contacted our customer support and we discovered that for only some people when they would try and run the app they would get a -1743 error indicating an issue with Apple Events being allowed. And when we test it there are no issues and it is only certain customers.So at this point I am completely at a loss. I have put in a support ticket with apple technical support but who the **** knows how long that will take. Sometimes it takes them weeks to respond. How in the world does this start happening out of no where. If anyone else is experiencing the same issues let me know. I have tried testing on different Mac Calatina versions both release and beta developer. I have tried different versions of the latest Xcode. All have the same result now even though they were all working perfectly as of last week.

I recently updated to Big Sur 11.0 beta. I am aso on Xcode 12.1. I have had this project for at least 6 months now with no issues. Yesterday it was working on now today when I try to launch the app the build succeeds and then the app never launches and it goes to a variety of different dyld' windows dylddyld::loadPhase5check: dyldstat64: dyldImageLoaderMachOCompressed::rebase: dyldgetattrlist: the most common of which that pops up when building is dyld_dyld_debugger_notification: and dylddyldstart: I have tried googling these and I am at a complete loss. I have no idea what to do or how to fix this. I tried turning off "Generate Debug Symbols" in the build settings and then i cleaned my build folder and recompiled and that worked for about 10 minute and then stopped out of no where again. I have no idea whats going on but this seems like a pretty serious Xcode bug.