"Waiting for Settings" happening regularly with LR Mobile since updating LrC to v12

[jmorg65]

I've only noticed this since updating to LrC v12, but I'm getting regular "Waiting for Settings" messages with photos in LR Mobile (iOS version) on photos which I've edited on LrC. Attached screenshots show the message. The only option is to keep waiting or overwrite all the edits that have been done. The screenshots were from 11/10 and some of them say that the edits were done in late October so almost two weeks and, for some reason, they have not sync'd over to LR mobile from LrC. I have even done a Rebuild Sync Data on LrC recently and it fixed the issue for some photos but not others. If the data hasn't sync'd in almost 2 weeks, unclear if it will ever do so and why on earth it would take this long to sync the information.

Unless v12 broke something that needs fixing, I assume there is a way to make this stop happening so that small amount of edit data are sync'd quickly as I've never encountered this issue in the past roughtly 4 years of using LR mobile until updating to v12. 

Anyone know why this is happening and how to fix it permanently? 

[Mathias72]

The solution for me is, that i select all photos in the grid and make a little change over "adhoc" for all pictures (adjustment clear +1). After this change it beginns to sync and wait til the end to switch back the last adhoc-change. It beginns to sync all pictures again, thats all. The problem is the amount of your pictures,many pictures need's a long time to sync, but

it is important that a small change is made to the images. I had no further problems with newly imported images

It's best to just do it overnight.

[freddyl43392669]

Got the same problem 

[umlautnord]

I think some folks allude to masking, but, the first thing to try is definitely @Jim Wilde 's suggestion of making small adjustments to force a sync.

However, I was having a lot of trouble with this that persisted for some images, and narrowed it down to images with AI-based masking and/or AI-based healing created prior to being synced to the latest version of LrC. They'd get stuck showing as syncing masking metadata in the LrC sync status, and show the "waiting for settings" error in LrM. That'd occur even if I never touched the image in LrC. I.e., situations where the image started in LrM, the mask was created in LrM, and the image synced into LrC. (LrC then seems to do some sync back up into the cloud as part of that process, which is what results in the problem.)

If the mask/healing was removed entirely, it seemed to work fine—fully sync, no LrM "waiting for settings" issues. If I created a mask anew after everything was synced with the latest version of LrC, it'd sync without issue. Note, the mask could not simply be removed via LrC history, that version synced successfully, and the mask reapplied via history—it had to be a truly fresh mask/heal. 

I'd check out if this is the issue on a couple of problem images. If it is the problem, it's obviously a giant pain to correct manually if you've got a ton of images with this issue. (You can at least ID them via smart collections in LrC.)

I was able to fix this in bulk because I had exported a backup of all originals with settings from LrM before starting a big sync down into a fresh LrC catalog—migrating from LrM only to a mixed LrC+LrM situation. Once the sync had completed except for these problem images, I removed/deleted them all from LrC + LrM, and reimported from the backups into LrM. That seemed to fix the issue for whatever reason. That backup was specific to my situation, though.

The parallel I can think of for folks starting primarily from LrC: It might be worth trying exporting as originals from LrC, deleting the image from the LrC catalog, and then adding the exported one? It should keep its develop settings, including the masks, but may force LrC to reevaluate the masks in a way that syncs properly. I don't know if that will work, but that's where I'd start. You lose your collection organization, and may lose other metadata—I don't know. If that doesn't work, perhaps try exporting the latest version from LrC and importing via a cloud app (e.g. LrD, LrW, or LrM).

But, basically, my ultimate conclusion was that previously created AI masks and AI healing were the issue—those images wouldn't fully sync out of LrC into the cloud, resulting in "waiting for settings" problems in LrM. Exact fixes may vary on your specific situation, but I hope this is helpful to some in ID'ing/fixing their issue, at least!

[nicklat14]

I can confirm this is the issue I'm facing here; I've spent hours trying to deduce the culprit, and this is definitely it. Adobe please correct this, it's a huge workflow killer. Thanks Umlautnord.

[jonathanp41403920]

I hope that I'm not being overly optimistic here but I've been almost constantly on the phone/chat with Adobe in the past 2 days regarding another sync issue (where LrC never seems to complete synching with the cloud even though the number of synched items in LrC and the cloud are the same). It appears that in the very latest version, (the one where Adobe introduced Generative AI removal v 13.3.1) they have also completely re-structured the sync architecture. It has caused my machine and LrC to run very slowly ever since I upgraded to 13.3.1 but they were apparently expecting issues and I'm told I'm not the only one who has them. It can take a long time (days in my case) for the sync to sort itself out but they assure me it will. Please don't ask me how, but my hope is that the sync architecture changes will fix the problems we've been experiencing on this thread. You never know!!