I currently have an architecture where I need to forward messages from the Safari Web Extension to another app through the App Extension. I understand from the docs on Apple, App Extensions are not meant to be used as a long running background task, but if it is just proxying messages, is it advisable to keep pinging the app extension to keep it alive and use it as a long running task in the background for proxying messages ?

I am trying to run a Main.xib file when an App extension starts from the Web Extension, but I am unable to see any output. I added the Main.xib to the App Extension's info.plist I assume when Safari runs and the app extension is called then the UI should pop up but I see no output.

I had created a Main.storyboard file and added a Window Controller Scene and View Controller Scene. I also created a ViewController.swift file and added it to the info.plist under NSExtension - NSExtensionPrincipalClass But when I launch the app extension by enabling the extension in the Safari Browser (host app), I don't see any UI popup for the app extension. Is there any step I am missing in this ? Also is there a main method for the App Extension or is it only the func beginRequest in the SafariWebExtensionHandler class? If i wanted another main like thread to instantiate objects for example., Where can I place them ? Thank you

I have a Safari App extension that has to communicate with another app that is outside the sandbox. I wanted to place an XPC service in between the two. Would it be possible to talk to an XPC service outside the sandbox with the use of temporary entitlements ? or are apple events the only way to go? If XPC service is possible, would it have to be an XPC exposed through a daemon process or can it be bundled with the non sandboxed app ?

I tried running a python binary that resides in the NSApplicationsScript Directory from a Safari app extension but it does not seem to run it, given proper entitlements. Is this a sandbox restriction for App extension ?