P: Default Metadata shows Original and Cropped as same dimensions

Something changed in Mac OS 12.3.1, and many people are finding they need to grant LR Full Disk Access.  See these instructions:

https://community.adobe.com/t5/lightroom-classic-discussions/lightroom-catalog-cannot-be-used-because-the-parent-folder-does-not-allow-files-to-be-created-within/m-p/12883223#M270829

Thanks @johnrellis I guess it is a little different but since de update. Its so strange now. I work on Mac; my two external drives are not readable in Lightroom since the updated. At the beggining also I reinstaled it, then verify catalogs, the issue is that my drives appear in green in Lt, but it can't find the files! Also since Friday, the date I update, I couldn't save in those drives. I can seee the files, open it, work on them, but when I tried to save, didn't let me do it. I have not issues before in any of the two drivesr mentioned. 

@Baltazar Villalobos, you have a different issue. Are you on Mac?

Hi, I don't know if the following is part of the issue. Since the update on 4/20/2022 Lightroom didn't recognize my external drivers. I have two and in both on them appear the legend "Didn't found the file". Please I need help I couldn`t work.

"this begs the question what are the engineers doing with features that require "Automatically write to xmp" to be selected?"

I don't think this is deliberate -- over the years, there have been a number of disparate bugs that could be worked around by manually doing Save Metadata To File or checking Automatically Write Changes To XMP.   I'm sure that the LR code that handles metadata is extremely complicated, and I don't find it surprising that saving metadata to file takes a different path through complicated, tangled code, which avoids or corrects a metadata bug.

There are many contributing factors: messy industry standards that have changed significantly over LR's lifetime, the addition of new file types, the addition of new Library and Develop features, attempts to improve performance, successive generations of engineering teams of varying abilities (regressing to the mean, as is typical for mature software products), and Adobe's public statements about focusing their product efforts of LR Classic on Develop rather than Library. 

@DdeGannes 

Unfortunately the bug list in LrC keeps getting longer an LONG term bugs are not getting fixed, even fairly severe ones.  I used to have a list of bugs I was keeping track of and would test at most of the releases but finally gave up.

@Bob Somrak this begs the question what are the engineers doing with features that require "Automatically write to xmp" to be selected? See this other bug.

https://community.adobe.com/t5/lightroom-classic-bugs/p-metadata-auto-sync-doesn-t-update-the-display-of-fields-in-the-metadata-panel/idi-p/12898391

@DdeGannes 

I think it would be just luck to find an obscure bug like this in beta.  When I first duplicated the bug I got lucky and picked a photo with the issue.  Several photos around it did not have the issue.

Surely LrC beta testers and engineers are checking using default settings to ensure the Application is functioning as designed?

Surely Adobe LrC and ACR beta testers should be working with default features to ensure the applications are functioning correctly.