@DTS Engineer Do you have any ideas how to solve the problem?

Thank you very much for the detailed information. I tested it, and indeed, it appears that the command security cms -D -i /path/to/your.app/embedded.mobileprovision shows the app group is empty in the provisioning profile: "com.apple.security.application-groups" => [ ] However, I haven’t found a way to update the profile to include the group. The profile is Xcode-managed, but I also manually created a development profile through the Developer Portal, and the group still wasn’t added, even though it’s activated for the identifier. Could this be a bug, or is there any other option available? Thank you so much for your thorough and competent help. I’m really pleased to have the chance to connect with you.

The secondary app is packaged in an app-like wrapper and worked perfect on macOS 14 without permission dialogs and it works in release builds on macOS 15 without permission dialogs. MyApp.app/ Contents/ MacOS/ MyApp MySecondaryApp.app/ Contents/ MacOS/ MySecondaryApp

@DTS Engineer I haven’t been able to resolve the issue, and I’ve also decided to skip trying full access permissions. The problem only occurs in the debug build. This setup involves a macCatalyst app that includes a secondary macCatalyst command-line app. Both apps share the same application group (com.apple.security.application-groups). The second app functions as a native messaging host for browsers like Chrome and Firefox, serving as the interface between the browser extension and the main app to facilitate data exchange. This setup was working without issues on macOS 14, but since updating to macOS 15, I keep seeing the permissions dialog. However, even when selecting “Allow,” the action isn’t being accepted or processed. In the release build, everything functions as expected without triggering any permissions dialog. Is there a way to debug or resolve this permissions issue effectively? Any insights would be much appreciated! Thanks in advance!

@zulfishah Please keep me updated if you find a solution. The prompts are extremely annoying, and worst of all, it doesn’t respect the "Allow" setting.

I recently started having the exact same problem. It occurs when I call browser.tabs.update({url: ''});. Then the content_script.js is no longer loaded. Looks like a bug, but I'm still looking for a workaround. It's definitely annoying!