Additionally, I've tried adding the RemoteAccessHostRequireCurtain property and then deactivating and reactivating Remote Desktop. No change.

Are you logged in as the user for whom you set the RemoteAccessHostRequireCurtain when you try to connect?

Can you send us the logs from the host from when it starts until a successful connection? To get the logs:

* Open a terminal: Press [Command] + [Space], type Terminal, and press Enter
* Copy the host log to a file: sudo syslog -k Facility org.chromium.chromoting > chromoting.log.

Attach chromoting.log to this bug.

> Are you logged in as the user for whom you set the RemoteAccessHostRequireCurtain when you try to connect?

Yes

Attached is my log. The relevant line seems to be:

> May 13 20:28:09 remoting_me2me_host[5530] <Error>: Invalid policy contents: RemoteAccessHostRequireCurtain: The value type doesn't match the schema type.

RemoteAccessHostRequireCurtain is a Boolean set to YES. On the Android app I am unconnectable with the message "Host failed to read the policy." I tried setting RemoteAccessHostRequireCurtain to YES as a String as well but no luck there either.

Deleted: chromoting.log 1.4 KB

chromoting.log 1.4 KB View Download

Thank you for providing more feedback. Adding requester "spqchan@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I think you need to specify "true" rather than "YES".

Oddly it seems to work without issue now (no update to the host binary, says  the log). Accordingly to the Xcode plist editor RemoteAccessHostRequireCurtain is still set to "YES" as a boolean. I haven't made any changes to that file since posting last. The plist editor only accepts "YES" and "NO" for boolean values. True and false seem to be automatically converted. I am not aware of how the values are stored internally but this seems consistent with the Objective-C YES/NO convention.

I did some more testing and it seems that completely disabling Remote Desktop and quitting Chrome is not enough to reload the configuration. This might have been the issue I was originally having. After doing a full reboot I can successfully toggle curtain mode (with a reboot required for each toggle).

The policy is read by Chrome Remote Desktop Host, so restarting that component should be all that's needed. Logging off and back on again will do that--no need to reboot.

I'm going to mark this WontFix since you can't repro it any more. Please follow up on this bug if the problem resurfaces.

For future finders of this thread I followed the same steps above combined with information from another post and that was to enable fast user switching (Prefrences->Users & Groups->Login Options->Show Fast User Switching as[] ).

After a reboot of my machine and logging back in then starting Chrome Remote Desktop from my phone my Mac quickly jumped to the login screen which is what it seems to use as the 'curtain'.

Hopefully this helps others out in the future.