Here are the specs of my machine:
Retina MacBook Pro (mid 2014)
macOS Sierra 10.12.3
2.6GHz Core i5
16GB of RAM
My hunch is that there’s a bug that’s only popping up in the latest version of macOS, but I’m not really sure. I’d love to know if others in the community are seeing the same thing I am.
Below are my error logs from trying to change the domain, in case that helps:
Feb 27, 2017, 1:35 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:35 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:35 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:35 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:35 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:35 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:37 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:37 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Feb 27, 2017, 1:37 AM EST - warn: [renderer/Prompt] Renderer
Error {
message: ‘114:165: execution error: No user interaction allowed. (-1713)\n’,
name: ‘Error’ }
Just a quick heads-up that this seems to be half resolved in Local 2.2.4, macOS High Sierra.
Changing a domain of a nun-running site is possible, but results in an endlessly spinning "wheel. Quit Local and restart: it wants to open the site with the new domain for “view site”, with the old domain redirected to the new domain for “Admin”, and with the old domain still set in wp_options for siteurl and home.
It does almost work with a running domain, though - site change works, but the SSL is wonky