I develop a ContentFilter network extension on Macos. It need call NEFilterManager's saveToPreferencesWithCompletionHandler function to take effect, which will pop up a Auth Dialog to let user to allow this filter. Does MDM support this kind of authorization to make user keep users insensitive

From https://support.apple.com/en-us/HT211860 said: To install a new or updated kernel extension in macOS Big Sur, you can do either one of the following: Instruct the user to follow the prompts within Security & Privacy preferences to allow the extension, then restart their Mac. You can permit users who are not administrators to allow the extension using the AllowNonAdminUserApprovals key in the Kernel Extension Policy MDM payload. Send the RestartDevice MDM command and set the RebuildKernelCachekey to True. Is There a way that user dont need to click "Allow" in Security & Privacy preferences ? The udpated kernel extension can be loaded after the user restart the computer?

After I upgraded to MacOS 26（beta）, my program caused the system to pop up a window as shown in the following picture. My application is a process with only a tray icon. I found that my tray icon is not displayed in the current version, even though I clicked the "Always Allow" button. Here are my questions: 1.Will this related feature remain consistent in the official release? 2.How can I create a cmd process that only displays a system tray icon (no main window) like Alfred?

During the release of our macOS App, we encountered the following issue: We need to support dynamic code loading of WebAssembly (wasm) inside our App, mainly by loading WebAssembly (wasm) binary modules. We discovered a problem: a wasm file is neither an executable nor a bundle, so it cannot be code-signed. Since our App needs to pass notarization, we have not set the com.apple.security.cs.allow-unsigned-executable-memory entitlement. Without setting com.apple.security.cs.allow-unsigned-executable-memory, loading a wasm module results in an “unsigned code” error that causes the process to crash. Could you please advise on what we should do to avoid this problem? Is it possible to apply for a special entitlement to allow com.apple.security.cs.allow-unsigned-executable-memory?

Since macOS 15.3.2, we have observed that when another window is moved near the App Store's install button, the button disappears. We have attached a related video in the Feedback submission here https://feedbackassistant.apple.com/feedback/20444423 Our application overlays a transparent, watermark-window on top of the system window, which causes the install button in the App Store to be hidden when a user attempts to install an application.Could you advise on how to avoid this issue?