“Popping Sound”

This is a good questions for the camera engineers and hope they can jump in and provide their knowledge as I am not in that team. I think you have a great understanding of that as you already provided the answers with two true statements from you: As per my simple understanding, the shutter sound on iOS is strictly controlled by the operating system and cannot be disabled by third-party apps. Also different countries have different behaviors by law. It follows the device’s silent/ringer state, and there is no public API provided by Apple to suppress this sound programmatically while the camera is in use looking at the documentation. I understand that you’re looking to manage the camera shutter sound within your hybrid iOS application. To clarify, Apple maintains strict guidelines around camera functionality to ensure user privacy and consistency across devices. As such, the shutter sound is a system-level sound that cannot be programmatically disabled or muted by t

Hello jaysack, Sorry for not following up on the additional info provided. The inconsistent behavior across two identical iPhones that @Regadas reported does sound like a bug. If you're seeing this issue as well, please file a bug report so our engineering team can investigate it in full. Do include device model, iOS version, and if possible, a focused test sample app that reproduces the issue. Once you open the bug report, please post the FB number here for our reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Filing a bug report will allow Feedback Assistant to notify you if and when the bug gets fixed. That is the case even if it is a duplicate of an existing known issue. If anyone else in this thread is experiencing this USSD dialer issue, please don't hesitate to file a report as well. Once again, we apologize for not replying sooner to this thread. For future reference, it's generally advisable to post replies rather than comments (which

Thanks for the post. Wow trying to go down the memory lane on iOS 14 and 15. If think you've diagnosed the problem perfectly. In my opinion, your issue is almost certainly because the com.apple.developer.carplay-driving-task entitlement is only available for iOS 16 and later as you said. To make your app compatible with iOS 14 and 15, you must fit into one of the legacy categories and obtain the corresponding entitlement from Apple. If your app has any audio playback features, applying for carplay-audio is the most common and straightforward path. If your app is for navigation, you’d apply for carplay-navigation. I would recommend to go to the Apple Developer website and request the appropriate CarPlay entitlement. https://developer.apple.com/contact/carplay/ Fill out the form, specifying the App ID and the entitlement you are requesting (e.g., carplay-audio). Follow this documentation https://developer.apple.com/documentation/carplay/requesting-carplay-entitlements I could be wrong

Hmm, that sounds pretty strange. If you don't mind to provide a stripped project to demonstrate the issue, I'd try to figure out what happens. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Hi Kevin, As per our tester, he explicitly ensured that the app was force-closed at the end of the day. However, as you correctly pointed out, the logs indicate that the app was never actually terminated by the system—it was moved to the background and then resumed the next morning. The challenge we are facing is that certain functionality does not behave correctly when the app resumes the next day without a normal cold start. The primary issue is with the SLM (Sound Level Meter) framework, which relies on audio sessions. In these resumed states, the audio session is not always reinitialized cleanly, causing our calibration process to fail and leading to the core issue we observed. To address this, we implemented a controlled, app-initiated exit in such scenarios to ensure the app always starts in a clean state. This approach resolved the issue successfully. More recently, we encountered a case where we did not even receive the applicationDidEnterBackground callback. We extended the

I’m not aware of any official documentation about time.apple.com. Given that, you have to treat it like an implementation detail. It sounds like your app really needs trusted timestamps. That is, if the time service went away, your app would cease to function properly. Given that, I recommend that you use a time service that’s documented to be appropriate for your use case, or something that you run yourself. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hello a.mclaughlin, As far as I know, AVAssetDownloadURLSession is the only available API to cache HLS playback- as per the AVURLAsset .assetCache property, The value of this property is nil if you haven’t configured the asset to store or access media data from disk. - meaning HLS video is not cached by default. One hacky workaround you can try is to set AVPlayer.actionAtItemEnd to .pause, then automatically seek back to 0 when it reaches the end. Have you tried any other video formats to see if they support soft subtitles in iOS? Do your HLS video subtitles use the AVMediaSelectionGroup and AVMediaSelectionOption classes covered in the Selecting subtitles and alternative audio tracks guide? Some subtitle formats AVFoundation supports include WebVTT, iTT (iTunes Timed Text), and others, in .mov and .mp4 files. Thank you for your patience, Richard Yeh  Developer Technical Support

Thank you for your question. The volume control of third-party applications is primarily managed by the user, not the developer. AlarmKit does not directly support volume customization beyond utilizing the system ringer volume. As far as I can see, there is no API in AlarmKit that allows for volume modification neither. Given that AlarmKit does not support volume control, consider using it to handle audio playback for alarms. This approach provides you with complete control over the audio, including volume settings. You can schedule local notifications to trigger an alert, and when the notification is triggered, use or to play your custom alarm sound at a user-defined volume. Hope this helps and answers your questions, you can file an enhancement request if you want. Albert Pascual
  Worldwide Developer Relations.

Hi, We're able to implement the speech framework. For some reason my app crashes when clicking Allow for the Speech permission pop up. Upon rebuilding it works fine, as the permission appears as granted.