We have a sandboxed extension that we include as part of our app bundle. In some workflows, the extension launches the "main" user-facing app. In Big Sur Update 6, once the extension has launched the app, and user double-clicks a file that our app is the default-handler for, the passed in file-path in our delegate's application:openFile: method is incorrect, leading to failure in opening the file.
E.g., if the actual file-path is ~/Desktop/foo.bar, the passed-in path is ~/Library/Containers/<extensionBundleId>/Data/Desktop/foo.bar
This bug seems closely related to the fact that the HOME env-var in the launched app is similarly messed up. Instead of $HOME being mapped to "/Users/<userName>", it's pointing to "/Users/<userName>/Library/Containers/<extensionBundleId>/Data". i.e., it looks to be inherited from the launching process (extension).
FWIW, I tried both -[NSWorkspace launchApplicationAtURL:...] and LSOpenFromURLSpec() APIs to launch the app, both resulting in the same behavior.
This is clearly incorrect behavior; will this be patched in an upcoming update?
Thanks
E.g., if the actual file-path is ~/Desktop/foo.bar, the passed-in path is ~/Library/Containers/<extensionBundleId>/Data/Desktop/foo.bar
This bug seems closely related to the fact that the HOME env-var in the launched app is similarly messed up. Instead of $HOME being mapped to "/Users/<userName>", it's pointing to "/Users/<userName>/Library/Containers/<extensionBundleId>/Data". i.e., it looks to be inherited from the launching process (extension).
FWIW, I tried both -[NSWorkspace launchApplicationAtURL:...] and LSOpenFromURLSpec() APIs to launch the app, both resulting in the same behavior.
This is clearly incorrect behavior; will this be patched in an upcoming update?
Thanks