Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

rbelusko

macrumors newbie
Original poster
Apr 14, 2017
7
2
I am using a 2018 Mac-Mini , which is updated to the latest version of Sequoia (Developer Beta 5 'aka 'DB5'), to use the 'iPhone Mirroring' application, which is displaying my iPhone 15 Pro.

I am using the Mac-Mini, as it has a T2 security chip, which is required for the 'iPhone Mirroring' app to work: my primary desktop computer is a Windows 11 PC.

What I have been doing is: using VNC on my Windows 11 computer, to remote-connect into the Mac-Mini, in order to use the 'iPhone Mirroring' feature. At first (Developer Beta 2 - aka 'DB2') on the Mac-Mini allowed me to fully operate my phone in 'iPhone Mirroring' mode. The experience has been absolutely wonderful, having my phone available on my desktop monitor, and I did not mind having a VNC session open to the Mac-Mini, which I otherwise had stopped using.

That is until I upgraded to the next beta :(

When I installed DB3, the keyboard suddenly no longer worked for the 'iPhone Mirroring' app, in the remote VNC session. All other keyboard functionality in the remote session is fine.

Then today I installed DB5, and now the mouse no longer works in the 'iPhone Mirroring' app either. Just like the keyboard, the mouse works on all other applications in the remote session to the Mac Mini.

So my question: is this an intentional feature which Apple has introduced, in order to block remote access to the 'iPhone Mirroring' app? Or is it a bug? Thoughts?

If it is an intentional security feature, are there any workarounds which might restore mouse/keyboard access to the 'iPhone Mirroring' app inside of a remote session? I am an advanced user and I accept the risk of reducing levels of security that Apple is otherwise enforcing by default (if it's a configurable option).

Thanks!
 
Last edited:

rbelusko

macrumors newbie
Original poster
Apr 14, 2017
7
2
After further troubleshooting, I was able to downgrade back to the MacOS Sequoia beta that was working, however I am still faced with this issue.

I believe the root was in the upgrade of IOS Public Beta 2 to Public Beta 3. I do not know how to downgrade this.
 

rbelusko

macrumors newbie
Original poster
Apr 14, 2017
7
2
This is fixed for me in the newest beta that was released today.

I'm not sure if it was the iPhone update, or MacOS, or both. But it works now 100%.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.