I made some progress, and the issue can be reproduced programmatically when using lower resolutions. That is, when a picture is taken at full resolution (3024x4032), the EXIF aspect ratio is the expected one, 28mm. However, as you lower the resolution, the FocalLengthIn35mmFilm value increases, linearly: 32, 64, 96, 177 (for 480x640 pictures) and 311 (for 352x288 pictures). The increase is indeed linear, meaning that I use the image dimension and divide the value to get the real focal distance - it works. Is this behavior expected? This is weird, because the focal length should not change with the resolution - should it?

The same issue can be observed with an iPhone 7 and iOS 15.8, using the same code.

Thanks for your reply. The code I am using is similar to the following (captureToFile function): https://github.com/flutter/packages/blob/d63629d7e2dad0c9b2f848d8ede398ef2e801cc9/packages/camera/camera_avfoundation/ios/Classes/FLTCam.m#L260 Any idea about what could go wrong? All other EXIF values I could inspect make sense, and there are many of them. Unfortunately, I don't have another iPhone at hand.

Thanks for your reply. The way I did it is that I first connected to Apple Store Connect using my development account, then I registered my personal account in the Apple Store Connect "Users and access" page. From there, I gave it the "Customer support" role, as it seems this role gives the least amount of control of app, as suggested here: https://developer.apple.com/support/roles/ However, when I connect to Apple Store Connect using my personal account, then access my iOS application, the amount of control I have on it is scary: it seems I can pretty much fiddle around every setting! This is not what I want - I would like my personal account to be able to access internal beta versions, but have near-zero access rights on Apple Store Connect. Is this possible?