• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Problem synchronizing folders using Mac Sequoia 15.0.1

Explorer ,
Oct 20, 2024 Oct 20, 2024

Copy link to clipboard

Copied

Prior to the upgrade from Mac OS 14, when I synchronized a folder in LR Classic, that folder updated itself correctly — Lightroom added any new images and deleted anything that was no longer there on my disk. After upgrading my OS, I also updated LR Classic to v. 14.0. 

Now, when I synchronize a folder, it sets the old folder image counts to "0" (no content) and places a new folder with the same name outside the entire folder hierarchy outline in the list on the left. AND there seems to be no way to move the new folder back into the hierarchy. I get an error message that the folder already exists in that location (even if I remove the old folder from the hierarchy).

I tried updating LR Classic to v. 14.0.1 but that didn't help.

So I reverted my LR Classic installation to v. 13.5.1 which had worked fine previously, but it exhibits the same behavior.

At the moment, the only solution I can see is downgrading my entire system back to Mac OS 14. Which is not going to happen. So I assume Adobe has to be aware of this incompatibility and is working on a fix.

 

Meanwhile, does anyone have a workaround for this?

ANSWERED MY OWN QUESTION!....

But I'm posting it here anyway in case someone else has the same problem. This is caused by a well-known bug: the Capitalization Problem. It was described (and solved) here back in 2018:
https://community.adobe.com/t5/lightroom-classic-discussions/catalog-same-photos-same-location-but-s...

I must have capitalized the name of one of the folders around the time I upgraded the OS without thinking it would affect anything — totally normal thing to do on a Mac. Last Friday evening, I spent two hours on chat with an Adobe tech to try to solve this problem. He had no idea what was going on.

Why on earth Adobe can't have solved this over the past 6 years, or at least alerted its tech support people and its users that this could happen, is beyond me.

 

TOPICS
macOS

Views

84

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation