UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Platform: 9592.96.0 (Official Build) stable-channel chell

Steps to reproduce the problem:
1. Create a Chrome extension that declares the "enterprise.platformKeys" permission in the manifest.
2. Host this extension somewhere other than the Chrome Web Store.
3. Log in to your Google Admin page.
4. Configure the extension to be force-installed for your domain's users.
4. Navigate to 'Device Management > App Management' and select your extension.
5. The switch to enable 'Allow access to challenge enterprise keys' is not visible.

What is the expected behavior?
I expected to be able to enable this policy via the Google Admin site.

What went wrong?
Certain UI elements (such as this toggle) appear to be made visible only when an extension is hosted in the Web Store, and Google Admin is able to parse the manifest.

Did this work before? No 

Chrome version: 60.0.3312.114  Channel: stable
OS Version: 9592.96.0
Flash Version: 27.0.0.130

Being able to host Chrome extensions locally during development greatly tightens the development loop, as it avoids the wait for an extension to be published (which has been observed to take multiple hours).  When developing an extension that requires policies that are only configurable when it is hosted in the Web Store, development slows greatly.

Perhaps an option could be added to make all configuration items visible regardless of usage or availability of the manifest, or an option could be added to configure arbitrary policy via uploading a JSON file?