Also happened to me this morning. Waiting for apple's phone support to open at 9 cst

Matt, didn't mean to single out Quinn per se, I've seen you here quite a bit as well. Thanks to both of you for your responses. That's unfortunate (because of the UI hurdles for users), but at least I know I'm wasting time going down this path.

I appreciate it, Quinn.

Wow, man. 6 years later I spent the ENTIRE workday on this and your answer was the fix. Thank you!

Stumbled here and the key is where Quinn says "and only those entitlements".

`         let process = Process()         let url = Bundle.main.bundleURL.path + "/Contents/MacOS/Child.app/Contents/MacOS/Child"         process.executableURL = URL(fileURLWithPath:url)         process.terminationHandler = { (process) in            print("\ndidFinish: (!process.isRunning)")         }         do {           try process.run()         } catch let error as NSError {             NSLog("Failed to execute ", error)         } `

I'm no expert but I thought the additions to <key>com.apple.security.scripting-targets</key> explicitly call out applescript targets is what the AppStore requires. As for why am I using AS at all? Well I could revisit it but it works great and this code has been distributed to customers with Developer ID-signed installers. I'm tasked with getting this on the App Store and I'm trying to touch as little code as possible.

Given the time already spent on this and the only two people who've replied to me both suggesting a design change I will go ahead and start reading about XPC. Thank you for your time.

Absolutely. The parent app is a persistent app that presents an icon and menu in the toolbar and is doing some tasks in the background. It's responsible for handling user activation and sign out with a server. The child process is a GUI that is started from the toolbar and presents the user with a control panel of sorts. The child app needs to know things that only the Parent app knows. So I'm achieving that right now with a simple AppleScript interface for me to query the parent. It works great. I hate that I might have to build an entire XPC service and framework for the few comms I need to support. My 1 day of just perusing XPC docs seems like it's more for doing one-off tasks than IPC but I haven't spent a lot of time yet. The daily tasks of the job have me busy.

I came here from google trying to resolve a similar issue but I don't have a file called embedded.provisionprofile anywhere in my .app folder. I also don't see it in other apps I've installed from the App Store. Did something change in the last year since this post was made where these aren't distributed any longer? Is there an equivalent way today for me to compare my entitlements against the prov profile?

This extensive writeup is exactly what I needed. I was able to build a test app that worked when bundled inside the main app and distributed via TestFlight. Thank you, Quinn. I have another stumbling block with integrating the real app but will make a separate post since it's a specific error

Thank you, that actually might explain some oddities I've seen during development/test

Yes, lots to read. For some odd reason I'm hungry for varnished waffles.

Ah, I see. Perfect, thanks again for your help!

Thank you!