Great. Thanks for the reply. That is good news. Looking forward to the fixed version of iOS 26.

Since WWDC has just started and all focus will now shift to iOS 27, I am worried that this will remain broken in iOS 26. We have implemented a workaround based on the sample code above, however it took a lot of work to make it behave like the original volume meters and even now it is only an approximate match and involved compromising some other parts of our app. I would like to keep this solution in place for the shortest time possible and return to the original API once fixed. Can someone from Apple please confirm that this is being investigated with a view to fixing it in iOS 26, or share any other info you can on this issue. This breakage has real, negative affects on the usefulness of our app for our users, as well as being bad publicity for iOS and Apple in general. Thanks

We are experiencing the same issue too in our video recording app. We use the averagePowerLevel and peakHoldLevel to provide the user with volume meters and this aspect of the app is now broken. Thanks for the possible workaround, eddiewangyw. However, I am not super keen on implementing a workaround - it might break other things since the audio and video capture aspects of our app are working fine. It would be good to know if this issue is being considered for fixing in iOS 26.5 or earlier. It does not seem to have been fixed in the existing 26.5 beta. I have raised a feedback report as FB22435501. Thanks.