“Popping Sound”

Hello, my app is designed for frequent travelers. It's kind of a collectors book. The user collects continents, countries, states, cities, sub-cities, rivers, seas etc. All the required data for that were well provided by CLPlacemark ... I also understand, that you try to provide good quality in the presentation of the (postal) addresses. The new API looks quiet good for this purpose. I never constructed a postal address by my own, as I understand the difficulties to build a proper postal address based on the users local needs. For that I used the postalAddress of CLPlacemark. Are there other ways to get this detailed informations? I really enjoyed the detailed data/Infos of the CLPlacemarks. Used to that richness of content and now seeing the puristic MapItem address strings is similar to be used to modern HDR-TVs and suddenly fall back to a Black&White TV from the 1960. So far new APIs were allways some kind of a better way to achieve something. Well some better, some not so good.. but it was always fai

When using App Intent, I noticed that we cannot process the image directly within the invoked UI. It appears that this is restricted by Apple’s privacy protections—any attempt to handle the data immediately results in the background privacy indicator showing a blocked status. Therefore, App Intent does not seem to meet our need to process user-provided images directly. This sounds like you implemented a UI snippet as part of your intent, and not all SwiftUI features are available in a UI snippet — for example, these snippets aren't interactive. Details here matter, so to discuss how you can build an intent that works for your needs, it'd be helpful to have a test project or test code that demonstrates what you tried and where you ran into trouble so that we can more fully explore this. — Ed Ford,  DTS Engineer

Third-party apps have been mentioned a few times, so I wanted to clarify what's going on there. Let me start by going back to the post that started all of this to explain what's actually happening here: When I launch the app, it indicates that the hub is not responding, and all of my devices are unavailable. One of the fundamental problems with all network applications is that: a) Users want to know whether or not something will work before they perform that action. b) Networking is an inherently high-latency activity with unpredictable results. Putting that in concrete terms, how does an app know that an accessory (or any network connection) is working, given that a hammer, shovel, or power outage could destroy the device or infrastructure the app is relying on? The app can check whether or not something is working by doing some kind of communication, but ALL that will tell that app is that the connection... worked in the past. It won't actually guarantee ANYTHING about the operation you're doing now. The an

Doc is not accurate. Navigate to Developer, then scroll down and tap on the sandbox apple account email. pop up appear. Then tap on Manage, scroll down and you would see Age Assurance

I am facing a severe audio routing instability issue when using CallKit and the Zego Express SDK on iOS. The problem is that the audio route immediately reverts from the Speaker back to the Earpiece, effectively disabling the Speaker button functionality. 📝 Are you able to reproduce the problem in our sample code (Speakerbox)? Observed BehaviorWhen the user taps the native CallKit Speaker Button, the audio route is correctly changed to the Speaker, but then instantly flips back to the Receiver (Earpiece), as shown in the system log captured via AVAudioSession.routeChangeNotification monitoring. 🧾 Log Evidence (Flapping Occurs in 0.4 seconds)The following log snippet clearly illustrates the system overriding the user's action (reason: 4) with an unexpected CategoryChange (reason: 3) event: I think this is a problem with the library, specifically because of this: with an unexpected CategoryChange (reason: 3) event: CallKit is tightly integrated with the audio system because

I also having an issue with AVSpeechUtterance on CarPlay, specifically on Wireless Carplay. Im getting an error IPCAUClient.cpp:129 IPCAUClient: bundle display name is nil or IPCAUClient.cpp:139 IPCAUClient: can't connect to server (-66748) after speechSynthesizer.speak(speechUtterance) and my audio is not being played or all the audio, including from other app audio become very choppy.

We are also facing similar issue the follow-up frames I send are not receiving any response. . Did you get any response from apple or breakthrough for this? As per my understanding, once initiate bootstrapping follow up frame and apple device respond with follow up frame. it may be pop up pin which need to use for PASN exchange later.

And when PTT notification arrives, saving the URL to the audio file in incomingPushResult, then downloading and playing that sound using AVAudioPlayer when didActivate is executed. It's working fine on the foreground, but when the app goes to the background, incomingPushResult is called as expected, but didActivate is not for some reason. Am I missing anything in my setup? Yes. The issue here is that you can't use AVAudioPlayer, as it does its own AudioSession activation. More specifically: It's working fine on the foreground. It works in the foreground app because the foreground app has inherent access to the audio system and can do whatever it wants. However: when the app goes to the background, incomingPushResult is called as expected, but didActivate is not for some reason. ...what happens in the background is that the same activation attempt then occurs and either fails entirely or succeeds (partially) but is then disrupted by callservicesd's own activation. Unfortunately, you'