Unfortunately I can't help you, but just as consolation -- I have pulled my hair out over exactly the same problem for a few hours in my game. It's pretty hilarious now that devices have no hardware controls anymore, which is bad enough, the SOFTWARE controls are now so "overloaded" and unpredictable that they essentially are useless, too.

This whole thing is pretty stupid in general. I mean, in 99% of cases, it's completely obvious why an app wants to access the camera. This should be optional at best. The world survived for at least a decade before this requirement surfaced.

Just wait until you're trying to implement a simple file selector ("Document Picker" in Apple parlance). The Apple documentation for it sounds like some kind of writeup on how to calibrate rocket engines, with words I've never heard and incredibly convoluted ways to deal with the file if it's returned. It also doesn't help that all examples on the net for anything are now for Swift, after I had barely learned Objective-C. So am I supposed to learn yet another obscure language now or what?

Don't bother, use a hybrid web app development toolkit. Native iOS development is so ridiculously complicated and convoluted that you'll want to die once every 5 minutes. Do yourself a favour and use something like React.

The problem is really very basic, and it's definitely Apple's fault, and Apple these days frankly doesn't seem to have a single UI/UX expert on site. It's the mere fact that App Store Connect lists screenshots by screen size, while Xcode lists the simulators by model. That is some serious UX b_/llsh1t.