P: No photos in selected folder (Mac)

Today I received the message that there is an update to 12.2.1. I installed it on my Mac24 and none of the problems

are solved 'no photos in selected folder' and all the Fuji film simulations gone... So I will roll back to 12.1 again

We have contacted some of you offlist. Please add your comment here if you face this issue.

Thanks,
Sunil

A few days ago, in another topic that I THINK has now been folded into this one, I spoke of trying to fix a friend's catalog that had problems (most likely) due to having 2 external drives with the same name.  It had also experienced the loss of images in folders discussed here.

We ended up creating a new, clean catalog and importing all her images.  BEFORE doing this, I ran the metadata status and fixed all the inconsistencies (hopefully) in her images, so all the metadata was saved to the images.

Two new things are happening and I'm not sure EITHER is related to this problem, but....

1.  She is missing keywords and develop settings on SOME images in Lightroom. 

I had her start Bridge, which she's never used, to look at some images, and it APPEARS (I'm not sure as she was struggling badly with bridge, our link was slow and spotty due to my current location, and she was having trouble understanding that I was attempting to verify what metadata is actually IN the images, so we'll try again) that at least SOME images have different keywords in Bridge than in Lightroom.  In some cases there MAY be keywords associated with files in Bridge that Lightroom does not display.

In Lightroom, her keyword LIST appears intact, but the "Keywords" palette shows no keywords, or a subset of what may be in Bridge.  And yes, I've set it to the keywords and containing keywords (?) setting. 

I'll explore this further the next time we Zoom, but I'm bringing it up only in case this is some bizarre side effect of what's going on - though I can't believe Lightroom COULD display different keywords, but...

2. While exploring the NEW catalog, she complained that her month folders (she does year/month organization) did NOT have all the images that SHOULD be in the months.  After further exploring, I realized that approximately 43,000 images that SHOULD be in month folders were instead in her top level folder.  I suspect when they were ORIGINALLY imported, it was done incorrectly, and they weren't put in the months.  Again, I don't THINK this is part of the ongoing bug, but in case other people start reporting bizarre behavior with organization...

I currently have her finding images in the top level folder by year/month (in GENERAL, her filenames start with YYYYMM), and moving them to the correct month.  Boring but not difficult, so she should have MOST of the images cleaned up in a few days.  I say "MOST" because of the following.

She has duplicates.  Thousands of duplicates.  I don't know HOW this occurred, but I've seen it before with other catalogs, usually from users that use both Lightroom and other tools like Bridge.  I her case she uses both Luminar and ON1 in addition to Lightroom.  There are files with a "-2" at the end of the name.  And -3, and -4.  AND, there are files with "-2-2-3-2" type appendages.  From what I've seen in the past, this is evidence of duplicates, and duplicates that have been duplicated multiple times.

SOME of the images in the top level folder ARE also duplicates of those in the year/month folders, so when she moves images to the correct location, she gets the error that some images are already there.

At present, since I'm not 100% sure she doesn't have different keywords on different duplicates (see 1 above), I'm NOT having her delete these duplicates, figuring we'll address those after as many images as possible have been moved to where they belong.

Unfortunately, as near as I can tell, Lightroom doesn't have a way to isolate the duplicate images - a text search for "-2" doesn't work using "ends with" in Lightroom, and using "contains" doesn't work because she has thousands of images with "-2" in a variety of places in the filename.  There's no "base file name" for the text search and it seems that Lightroom is using the file extension as the end of the filename.

In Windows, I have tools that would easily let me find everything ending with the duplication indicators and delete them, then resynch Lightroom, but I have no idea how to do the equivalent on a Mac.

I discovered the same, all fuji simulations are gone.

I am still having issues.  I am sycronizing all of my folders.  I have to do it one by one, but it seems to for some folders, but when I close and reopen, there are some files I need to redo.  I really hope this gets fixed soon.

"I have discovered that Lightroom has removed all the Fuji film simulations."

Please start a new topic for that issue.

Just to add to my upgrade to 12.2 woes, I still have two orphan partial folders from external after reinstalling v12.1.  In addition I have discovered that Lightroom has removed all the Fuji film simulations.  I spoke with a friend today who has not had a problem with v12.2 until he discovered that also is having issues with theFuji film simulations.

Suggestions?

@Rikk Flohr: Photography:

1. Please change the name of this thread to "No photos in selected folder (Mac)", which is the error message that people are searching for and right now many are not finding this thread.

2. Please change the name of this other thread:

https://community.adobe.com/t5/lightroom-classic-discussions/no-folders-in-selected-folder/m-p/13626566#M313373

to "Windows: No photos in selected folder".  Only one person on Windows has reported that message, but many Mac users are ending up there instead of here.

3. Please pin a post in this thread recommending users to roll back to LR 12.1.

I had a similar problem as what Abigail is describing, where I kept getting the message "no photos in the selected folder" for all the images on my external hard drive.  I tried reverting to 12.1 and it didn't work.  The developers asked for a copy of my catalogue.  They repaired it and sent it back to me and now it runs in 12.2 with no issues.  They also mentioned they are working on a 12.3 release that should address this issue.