Can’t unlock the MacBook Pro with Apple Watch while displaylink is active
Can’t unlock the MacBook Pro with Apple Watch while displaylink is active because the machine thinks the screen is being shared. Please implement a flag to the OS that displaylink is not screen sharing but is an authorized virtual display.
Delivered in DisplayLink Manager 1.5. Details available from https://support.displaylink.com/knowledgebase/articles/1977291 For individual feedback on this feature, please reach out to firstname.lastname@example.org as individual replies are not possible via the idea board.
Mark Pearl commented
Same issue. Really the response from DisplayLink is not appropriate. DisplayLink please fix your stuff and stop passing the buck.
I am using macOS 12 Beta and also DisplayLink 1.5 beta drivers. Apple Watch unlock is checked but does not work.
Jan Ernsting commented
Installed 1.5 Beta: Watch Unlock works 🎉 Thank you for making it work!
Same issue masOS Big Sur 11.5. Sorry this is not acceptable. You folks need to up your game. If this was a $20 piece of hardware but I paid over $300 for the version that I have
M Tauras commented
After years of using other docking stations / DP adapters that do not use what can only be described as a hack -- relying on MacOS screen recording to add additional ports -- I was horrified by all the issues I now have:
Cannot close Intel MacBook Air and use clamshell mode (I understand this is being worked on)
Cannot play protected video
Cannot unlock using Apple Watch
Cannot use Night Shift
The correct solution is to completely re-write your software to not rely on a hack. If the hardware does not allow this, then all these devices need to be scrapped.
Please advise if development of a completely new driver is in discussion (a minimum) or active development (what I would assume is happening).
This is a BS response as its the DL methodology that causes this condition, if you switch to the raw, legacy driver without manager, this goes away. Quit pointing fingers and fix your sh!t!!!
SOOOOO Glad I found this thread. Now that I see the DisplayLink's response, I aim going to go and purchase a dock that actually does not use their driver and will not be using any of their products until they can get things fixed. it is a classic case of "Not my problem" which never helps anyone, but instead only succeeds in putting the customer in the middle with issues that ultimately are out of their control and that we are unable to fix. BYE!
It will be a great feature to bring back Apple Watch unlocking.
Same issue (BigSur 11.2.3)
For me it would also be ok if the DisplayLink display was off/black during unlocking.
same issue in BigSur 11.2.3 - the message on the screen is "Your screen is being observed"
Same issue, Big Sur 11.2.1.
Greg Hart commented
Same issue here on Big Sur 11.2.1
I understand this is an Apple issue and very hard or impossible to fix for you guys. Would it be possible to add a option to "disconnect" the DisplayLink Display during screensaver/sleep? This way the screen would not be shared during the unlock fase.
Dear Wim, yours sounds like a classic "kastje naar de muur" reply. If Apple needs to solve this (and who are we to judge), could you instigate this?
Please fix this, super lame that the DisplayLink drivers block this feature.
Mydisposable Gaccount commented
Same here. I'm putting up with it for now as DisplayLink drivers are the best solution for connecting two external extended displays to a 12" Retina Macbook (the one with only one USB-C port). If DisplayLink can fix this, please do so. I'm running Mojave and am connected to a Diamond Multimedia Ultra Dock Dual Video.
Craig Behr commented
same issue here, was going to recommend these t others but will have to look for a different solution.
Anyone found a workaround?
Will Koffel commented
I'm suffering this annoyance with a new DisplayLink powered hub.
This known restriction sure makes the homepage promise of "forwards and backwards compatibility for USB-C hubs" sound like straight-up false advertising. If you absolutely refuse to address this in the drivers, then how about at least updating the product promise prior to a class-action suit requiring it?
Matthew LeBlanc commented
Yes, I have this issue too
seriously guys fix the damn driver