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

LrM sync issue error - "Code: T20200121; Message: xmp develop sha256 mismatch"

Participant ,
May 26, 2024 May 26, 2024

Copy link to clipboard

Copied

Hi - 
 
I have run into some unexpected LrM/LrD sync trouble after the recent updates, leading to the below error. I was making some edits on LrM (iPadOS) to Smart Previews synced up from LrC. Everything seemed to generally be going fine. Changes synced across as expected, though some images weren’t always properly changing albums in LrM when moved in LrC. At one point, I switched back to Edit in LrM for a couple of those images. I'd changed Edit settings on them a few minutes prior. I received a "Settings could not be loaded" error. "Error Code: T20200121; Message: xmp develop sha256 mismatch." Screenshot below. Issue was originally for 2, but now 3, images.

 

IMG_0853.png

 

 

iPad LrM shows sync progress for 3 images, but is moving insanely slowly—after 3 hours it is at 98%, and has been there for maybe an hour. Internet connection is fine. Some other images and album/collection membership do currently sync fine between LrC, the cloud, and LrM—it’s not a totally broken connection.

 

I could try to wait to see if the iPad sync % someday hits 100% and fixes the issue there, but it seems more systemic. As noted, a third image joined the original two, while I was troubleshooting, and troublingly, there aren’t just issues with the iPad.

 

I’m also seeing the exact same album membership issues for the same problem images when I open/sync LrD (or LrM on an iPhone). I don’t yet see the Settings error on those platforms for the problem images at this point, but haven't tried to make any settings changes there. I haven't used LrD much/at all with these images. Given the same album membership issues are present despite that, I suspect I'd eventually run into the same problem.

 

Interestingly, LrW is matching/syncing with LrC completely as expected in terms of album/collection membership, develop/edit settings, and metadata. LrW is not throwing the Settings error in Edit for the problem images, or indicating any sync errors overall. LrC is not stuck on any sync and is not indicating any issues. The problem seems to be between whatever powers LrW ("the cloud?") and LrD/LrM on my devices.

 

Common denominators on the images: They're are all HEICs locally in LrC, but it’s a small enough sample size that I don’t know if it’s relevant. (I'm also working with DNGs in the same group of ~15.) They all also have some sort of AI usage/application. The first two have generative AI removals; the third one has AI object detection based masks (all AI-based masks/remvals were originally created in LrC).

 

I'm happy to interface directly with someone at Adobe with asset IDs and such if helpful to trace the problem/error. I'm extremely concerned the issue might continue to grow, especially given that it's not just the iPad acting abnormally.

 

Thanks.

 

----

 

System:

 

  • I have my collection/library in LrC (v13.3) on Sonoma 14.5 on a 13" MBP M1 2020.
  • I was editing smart previews synced into the cloud on LrM v9.3.0 on iPadOS v17.5.1 on an 11" iPad Pro (2nd gen).
  • LrD on the MBP, in which I see the same album membership issues as the other products, is v7.3.
TOPICS
iOS: iPhone , iPadOS , macOS

Views

95

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
Participant ,
May 26, 2024 May 26, 2024

Copy link to clipboard

Copied

Moving this with Adobe support directly, but if anyone has seen similar (essentially, Lr Web and LrD/LrM getting out of sync; Classic in the mix; completely starting with a fresh install of LrD/LrM removed the settings errors but did not totally fix the overall issue), would welcome any insight. 

Votes

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
Community Beginner ,
May 27, 2024 May 27, 2024

Copy link to clipboard

Copied

I am getting the same error on random images. All the images have AI generated edits and blur. iPad IOS 17.5.1 Lightroom Mobile 9.3.0

Votes

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
Participant ,
May 28, 2024 May 28, 2024

Copy link to clipboard

Copied

LATEST

Urgh. Frustrating. @davidwagoner , are you seeing the same behavior where LrWeb and LrClassic are fine/in sync/no errors, but it's just LrM where the error/problems are? And are they any specific file type—DNG/HEIC/JPG?

 

FWIW, resetting LrM entirely by deleting LrM on the iPad/reinstalling/completely re-syncing the full library reset the image back to whatever was in LrW/LrC and removed the error. Obnoxious and time consuming but effective as long as you didn't have a ton of edits waiting to upload out of LrM. However, my album membership sync issues remained for the images (they didn't get removed from albums they were not in in LrW/LrC), so there's still something going on.

 

Re AI—I recall in LrC v13.2, there were sync issues with images that used AI-based masks/removal/etc. But, those were between LrC and the cloud. It'd just get stuck waiting for settings in LrWeb/LrM/etc, and never finish syncing in LrC. You could fix it by removing any pre-v13.2 masks/edits and re-creating them in v13.2. This time, some of these images only had v13.3 AI edits. Removing all of them on one image did not fix the album membership issues between LrC/LrW<>LrM/LrD, so there's still something else going on. Maybe it's triggered by the AI stuff, maybe not. I'm not going to test further until Adobe Support digs in more. As much as I want to keep trying to figure it out myself...

Votes

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