Big Sur Update 6: File-paths messed up after app is launched from sandboxed extension

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

This is clearly incorrect behavior

I’m not going to argue with that (-:

will this be patched in an upcoming update?

Have you already filed a bug about this? If not, I recommend that you do so.

Please post your bug number, just for the record.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com" (r. 68569555)
Filed bug #FB8671424
Hi Quinn,
Any updates on this issue? We are wondering if we should actually put in a workaround for this issue.
Note again the bug #FB8671424.
Thanks

Any updates on this issue?

Nothing concrete that I can share right now.

We are wondering if we should actually put in a workaround for this
issue.

I don’t think that’s necessary. This problem is affecting a wide range of apps and is definitely being treated as a priority.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

Nothing concrete that I can share right now.

If I’m reading the Radar right, this should be fixed in 11.0b7. Please re-test.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"
Hi Quinn,

If I’m reading the Radar right, this should be fixed in 11.0b7. Please re-test.

Upgraded to Beta 7 (20A5374g) from Beta 6; we are unfortunately still seeing the issue.

Also I don't see any response from Apple on the bug (FB8671424). Would it be possible to post updates / current status / ETA of the fix, etc either here (on this post), or on the bug? Would be really appreciated!

Thanks
Vivek

Big Sur Update 6: File-paths messed up after app is launched from sandboxed extension
 
 
Q