New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unbind plugin from assistant #4
Comments
If you don't want/have to share state between plugin instances then there is indeed no need for the DPA. As for how to unbind, the code is pretty complicated at places as you can see, my suggestion for you would be to start by looking at the calls to |
Thank you sir, that's really quick response. In the SDK plugin export (AppleCMIODPSampleNewPlugIn), looks like almost every line of code has assistant involved, do we just need: Great appreciate your response. |
Right, in *Caveat: notarized apps with hardened runtime which didn't explicitly opt out from the "library validation" feature WILL NOT LOAD 3rd party code, CMIO plugins included. Since Photo Booth and FaceTime already ship hardened on Mojave, your plugin may be discovered by them but they will refuse to use it. Similarly, if e.g. Zoom decides to release an update in which they ship a notarized, hardened app, then that's the end of the line for your plugin. I've already tried to get information about this from Apple but they refused to provide any insights on the future of plugins. Hopefully the upcoming WWDC will clarify some bits. |
Thanks a lot, that's very helpful. |
Hi stang, I am stuck in that. Any help is thankable. |
Is there anyway to untie with DPA? if the virualcam doesn't need access hardware, the kext will not be necessary, I also don't want DPA, according the document, looks like the DP plugin shall work with it self without DPA and kext (I use TCP/IP for the source of the video frames).
If you could provide pure working plugin which could find by app (WebRTC, Zoom etc), it will be great!!!!
The text was updated successfully, but these errors were encountered: