P: Unable to advance to the next photo

@Sameer K any news here? We are paying yoou know? And it's also too latte to go back to 12.5... You may be surprised about howm many (me neing first) may cancel subscription moving to a free usage (and I know that you know iit's noot hard to uuse LrC for free).

Well my subscription is about to end and given these many recent problems I may decide to go back to a "free usage" of LrC...

From what I understand, ADOBE engineers can't find and fix the global problem yet. And it is very bad that they are silent about it now. Many handlers are suffering from this. If the problem is not solved soon, handlers will have to notify all their clients to roll back to version 12.5. But in this case they may lose their work, clients and money! ADOBE - hurry up please !!!

@mijbil250456 That's too bad.  I hear you about the loss of productivity because of this issue.  It's been significant for me as well.

Software development is complicated.  But it's surprising and disappointing that a bug of this nature would make it through internal testing stages and be released to those of us with businesses and livelihoods that depend on reliable products.  It's especially disappointing that the issue still hasn't been fixed after this long.  With the resources Adobe has, what's taking so long?

I'd guess that I'm not the only one who would appreciate if Adobe said something more than "we're aware of it".  It would be helpful to hear "this is our priority and we expect to have a fix this week."

@FrostyOfTheNorth @clib Looks like I spoke too soon - Like most of the apparent workarounds I find, they seem to work for a short while, before the gremlin reappears. It's as if the more I edit, the worse it gets, to the point where now it is on every single image, and on the Loupedeck too. It's driving me mad. I totally agree, the only solution is for Adobe just to fix this. As I've said before, it's probably the simplest function in Lightroom, and it doesnt work.  I've now edited 6 weddings with this bug, it's driving me mad. It's adding about 20% to my workflow in terms of time and I'm tempted to send Adobe the bill. 

@mijbil250456 I use a Loupedeck CT and can confirm that the issue occurs just as often and consistently as it does when using the arrow keys on the keyboard.  The Loupedeck arrow keys are set up to use "Navigate Left" and "Navigate Right". Presumably, that's sending LrC the equivalent to left and right keyboard arrows.

I do see that the Loupedeck software has an option for "next selected photo" but not for the previous photo.  I'm guessing that's because the SDK does not open up that option.

The solution here is for Adobe to fix this bug promptly.

mijbil250456 ... there is an SDK command for advancing to the next photo.   I am guessing this is what is being called when you map your arrow key to "next selected photo".

Further observations - I use the Loupedeck, and if I program the right cursor to next selected photo, then I can go through without any issues at all. This is in theory the default on the Loupedeck and should be the same as the right cursor on the keyboard, yet using this I don't see the bug at all. It's only when using my mac keyboard that the issue shows. 

I can confirm the issue occurs while using the SDK to make slider adjustments.   I have users of LrSuperKeys reporting the issue of not being able to advance to the next photo if they use the plugin to make adjustments and then use the arrow keys to advance.

Further testing observations - it isn't the cache, as the more I edit, the more the problem appears, and emptying the cache no longer works. I edit with smart previews for speed, with the folder where the originals are kept being renamed so that LR can't see the originals, and uses smart previews only.  Reverting the folder name back to what LR thinks it is looking for and allowing to to see the originals,  it looks like the issue is there, but it does eventually move the the next image. However, it is painfully slow, to the point where it is quicker for me to toggle back and forth with the bug than wait for Lightroom to look at the original and smart previews. Even though I have 'use smart previews for editing' selected in preferences, LR seems to still want to look for the original.