Posts

Post not yet marked as solved
5 Replies
jaroslavqwerty, I don't think the application would flood the system with popups if it would always return .replace. The system popup will only appear if the system extension last requested on the system is of a different version to the one you are requesting now. The delegate method wouldn't be called anyway if the versions are the same, as mentioned in the method documentation. I always return .replace in my extension. In my experience, it seems that nothing happens to the currently loaded extension if you make more activationRequests after the first one. Another reason you might want to always answer with .replace is that an application can uninstall the corresponding system extension loaded on the system only if it has the same version as the system extension embedded in the application. So choosing not to replace the extension might mean you end up without any way of uninstalling the given system extension (as far as I can tell). If you are seeing a different behaviour as described in this comment, please make sure that developer mode is turned off (run systemextensionsctl developer off in a terminal)
Post not yet marked as solved
2 Replies
I've filed a suggestion through Feedback Assistant about this. The submission number is FB8978333.
Post not yet marked as solved
5 Replies
I've submitted a suggestion with a similar description as this post through Feedback Assistant on the 11th of December 2020. The suggestion number is FB8936914. It has not received any response as of now.
Post marked as solved
3 Replies
Hello bweinsteinThank you for your answer. I have tested the posted code and some other extension on macOS Catalina beta with regular Safari and Safari Technology Preview. It seems to work fine on either as I haven't been able to reproduce the bug.I've also done some testing on macOS 10.14 with Safari Technology Preview, but it seems to function rather wierdly with it. I don't think the same issue happens, but some calls to API methods that use completion handlers don't seem work.I'm not sure how related to the original issue this is, but I do have another question. On all testing I've done, including on macOS Catalina, from time to time I get this error in the XCode console: "Error connecting back to host app: NSCocoaErrorDomain, code: 4099" and much more rarely the same error but with code 4097. Is this message related to the original problem? What causes it?Thank you for your time.