Popping Sound

SOLVED … by myself. Resolution is as follows: In the Device and Simulator Windows (where currently my right-pane top-area is blurred), click context/right-click like with intention to customize toolbar. Then the pop-up for toolbar-customizing like icon-only, icon and text , text-only appears. Choose something other than icon and text (‘Icon and Text’ will blur the top-part!!!). e. g. with Icon only setting —> all looks fine as expected. So, Apple, please fix this, other users will also trap into this. Completion: Do not set Toolbar to ‘Icon and Text’ ps. I don’t know how this initially happened to me. No clue.

In general, there is no way to continuously run a watchOS app in background for long time, if it doesn't have an active background session (such as workout, audio, or location). There is no way to directly access the heart rate sensor data on an Apple Watch either. You will need to go through HealthKit. How background tasks and HealthKit work on watchOS was somehow discussed here and here. You can take a look if they help. If your app is for research purpose, however, you can probably use SensorKit to access the heart rate sensor data. Access to those data types is limited to research uses and requires an app to have a private entitlement, which is reviewed separately for each study. See Accessing SensorKit Data for more info. You can also check if ResearchKit can help. Best, —— Ziqiao Chen  Worldwide Developer Relations.

I had been too swamped to be able to continue this conversation because of the highly prioritized work related to WWDC25, and after that I lost the track of this thread. Sorry for that. Thanks to another developer reaching out via DTS with the same issue, I am now picking up this thread, which hopefully is not too late. I'd like to confirm that I can now reproduce the issue. As folks have mentioned, the issue happens only in an Xcode project using folders, not groups. I've always used groups which helps me better organize files logically, and so had not seen the issue before. Xcode 26 Beta 6 doesn't fix the issue. Before the issue is fixed from the system side, the workarounds folks mentioned, like using groups instead or giving the new model version a name alphabetically ordered to the last, sound good to me. Best, —— Ziqiao Chen  Worldwide Developer Relations.

The main problem we are currently facing is that we cannot access the camera and transmit audio. We seem to have managed to do this through LiveKit, but it needs additional testing. Maybe someone knows how PersonaParty or TelePeeps do it?

It sounds like badgeLabel is the API you're looking for.

Is that the exact wording of the message? It sounds like your app has code that checks a backend service and has logic that determines when to display such a message that you'll need to debug. — Ed Ford,  DTS Engineer

So, let me start here and correct a basic misunderstanding: Even the app is not started yet. Fundamentally, CallKit is an interface framework, albiet a very specialized on, not a calling framework. In other words, the ONLY reason the user app ever sees the incoming call UI from your app is because your app told the system to show it. By definition, anytime CallKit is active, your app is running. hi Kevin, actually my question is all about the audio call only. So basically my concern is there anyway when user slide to answer the audio call, then they unlock phone, can we open the app to foreground? Why? Why do you want to this? The direct answer here is no, that's not possible, however, that's basically because video call is the call metadata CallKit uses to determine what should happen when the user unlocks the phone. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

A framework is a fancy wrapper around a shared library. Shared libraries have numerous benefits on Apple platforms: They can help reduce build times. If the same code is used by multiple programs in your product, like an app and an app extension, putting that code in a shared library can reduce the product’s size. If those programs can run simultaneously, a shared library can reduce your product’s memory footprint because only one copy of the code is loaded at a time. In some cases — and this is particularly important with Objective-C — using a static library can result in incorrect behaviour at runtime [1]. Oh, and when you bundle a shared library into a framework, there’s one more benefit: A framework can have resources used by the shared library’s code. Having said that, they’re not the right choice in all situations. And that brings me to this: [quote='798530021, raunits, /thread/798530, /profile/raunits'] However, I have found that the bundle size is more for Project 2 as compared to the bundle size of p

hi Kevin, actually my question is all about the audio call only. So basically my concern is there anyway when user slide to answer the audio call, then they unlock phone, can we open the app to foreground? Even the app is not started yet.