OSX 10.11.6. I can't select and Empty watched folder, if I can't access the Auto Import Settings. It still imports automatically based on the old settings, but I can't change anything or select a new destination folder. When I go to the File menu and select "Auto Import Settings" nothing happens.
I reproduced this issue using B Field's catalog today (but couldn't reproduce it with my own in the same machine) and submitted it as a bug internally. Preference reset didn't help. Manually removing the auto import settings from the catalog (NOT recommended!) did allow the dialog to open, and then it failed again when they were set again. Bug reference LRD-4194222.
_______________________________________________ Victoria - The Lightroom Queen - Author of the Lightroom Missing FAQ & Edit on the Go books.
Thank you. I won't bother with a preferences reset then. I'll wait. While the auto import settings is important, I can still use Lightroom 2015.8 and I can use workarounds to import files.
Thank you from me too. I was worried about reseting the preferences in case I lost the preexisting folder set up. I'm currently auto importing to the job folder from last week then moving the images to a new folder at the end of the shoot. Not a great solution but it's workable and way better than losing all ability to auto import.
Have the same issue and although it is not a big issue for me as I always import to the same location then move them afterwards to separate folders, but it is still annoying. (MacPro El Cap Lr 2015.8)
I reset preferences, and when I opened LR I could access auto import settings just fine. Then I relaunched and opened my everyday catalog. Now when accessing auto import settings I get the same error message. I then optimizing my catalog to see if that would help. No change, I still get the error.
I am getting this same error with macOS 10.12.2. Even without trying to change the settings, Auto Import is no longer picking up new files added to the previously configured folder.
My issue was merged with this one. Just to make it clear, auto import has stopped working on my config, AND I cannot access the settings. I say config because it will work on a new catalog, but not on my 150,000+ image, everyday catalog.
Win10, beefy hardward, LR2015.8
If an export of system info would help anyone, please explain how I can upload that. Thanks for your help. I can see the agenda is full.
The engineers have a catalog that they've been able to reproduce the issue on, so a fix should be forthcoming. In the meantime, if you rely on Auto Import, you might want to roll back until that fix is available. https://www.lightroomqueen.com/roll-back-update-previous/
_______________________________________________ Victoria - The Lightroom Queen - Author of the Lightroom Missing FAQ & Edit on the Go books.
Same problem for me with LR2015.8 release -- access to import settings was working then suddenly was inaccessible with the same error: Unexpected error performing command: ?:0: attempt to index a nil value. Did an uninstall and reinstall via Creative Cloud app to no avail. Using a prior version in the meantime. Windows 10 Pro 64-bit Core i7-3820 CPU@3.6GHz, 16GB RAM, NVIDIA GeForce GTX 670
Same problem for me with LR2015.8 release -- access to import settings was working then suddenly was inaccessible with the same error: Unexpected error performing command: ?:0: attempt to index a nil value. Windows 10 Pro 64-bit Core i7-3820 CPU@3.6GHz, 16GB RAM, NVIDIA GeForce GTX 670
It works with one Catalog, but not another. I made a new catalog, imported everything from the old one. And it started working again 🙂 The I updated the DNG metadata, and it stopped working again 😞
Adding my case with W10 to the list too. Resetting preferences allowed to access auto import. Reload of catalogue resulted in same error message, greyed out "enable auto import" and "attempt to index a nil value" when trying to access settings.
Also getting same message problem. I have W10. When I click on "auto import settings", I'm getting the message: Unexpected error performing command: ?:0: attempt to index a nil value.