Hi @hhaceart absolutely no worries! I have installed beta 2 this evening and it actually seems to now be resolved as Apple have promised! It’s not daytime here but I’ve tried under the brightest bulb (grow bulb for my lemon tree) I could find, and which previously triggered the issue! Let’s just hope it remains fixed until GM 👀

Unfortunately this has been made significantly worse in the iOS 18.4 developer beta (Build: 22E5200s). I have updated our feedback, but it seems this has gone entirely the opposite direction than we would have hoped: The issue now occurs even in dark environments (pitch black in fact) and also occurs even with auto-brightness a11y setting disabled. This will be absolutely killer for our app if it gets released in its current state!

Hi @hhaceart! I'm so sorry for the delay in replying to this. And apologies you're experiencing the same issue. Apple originally came back to me and stated it must be something in my code based on the sysdiagnose logs we provided to them, so I then wrapped the setTorchMode call in a measure function: let continuousClock = ContinuousClock() let torchTime = continuousClock.measure { power == 0 ? device?.torchMode = .off : try? device?.setTorchModeOn(level: power) } print("Time to toggle torch with AVCaptureDevice API", torchTime) and provided them the results from this, clearly showing the same issue you're experiencing. We have just heard back from them to say the issue is resolved on the iOS 18.4 beta, but contrary to that we have heard from users that iOS 18.4 actually makes it worse! I am in the process of installing the developer beta now and will feed back.

A further update after getting some analytics around this into our app: It isn't related to the adaptive true-tone flash, rather it occurs on any device with dual ambient light sensors. We still believe it's only an iOS 18 issue, but may also be present on iOS 18.0.1 The issue is not yet resolved on iOS 18.2 beta

Just an update on this, another way to fix it is to setup an AVCaptureDeviceInput and AVCaptureVideoDataOutput, attach them to an AVCaptureSession and call startRunning on the session. Presumably this limits the changes to the torch so it can be used as a camera flash more effectively. A less than ideal solution, as it will involve hand-holding of users to explain why we require camera permission, and will potentially also be picked up on by the review team too!

Hi Albert, Thanks for your quick reply! I have to say I was half expecting this to be the answer, but a small part of me hoped it would not be the case. It makes so much sense to have these controls for external cameras too, in particular I have a "full screen" mode in my app, and being able to use the camera control button whilst in that mode for configuring things such as shutter speed, ISO, aperture, and for actuating the shutter would make it such a better user experience! Instead users have to jump in and out of full screen mode to adjust any of these shooting settings. They are not particularly creative ways as far as I can see, they will just allow a more seamless interaction with the external camera over WiFi, make the shooting experience less cluttered, and allow users to use more of the screen real-estate for composition! I have submitted an enhancement under FB15100641 requesting this. I do have a further question, do you know how much of the AVCaptureSession process I would need to do in order to open up this functionality? And how much draw that would have on CPU and memory usage? I am half tempted to setup an AVCaptureDevice but just not render it in a preview layer in order to open up this functionality. Perhaps too you could speak as to whether that would lead to rejection at the review process stage? Perhaps there's someone I could speak to at Apple regarding this, to get it pre-approved or at least have a discussion around it? Simon

Hi Andrea, curious if you had any luck or a play around with this option? I've just discovered it myself, I'm scheduling a new connection in a similar way to you but also wondering if this is a better option! All the best, Simon

Did anyone ever get any intent donations to show? Having the same issue on debug builds, about to get a build into TestFlight but @Gong it looks from your comment that you haven't seen any actions donated at all for a whole year even with app live on the store!? Did you ever get to the bottom of it? I'm wondering about submitting an TSI request...