Popping Sound

I’d like to clarify your requirements here: [quote='786314021, PixelRothko, /thread/786314, /profile/PixelRothko'] two users see in real time, where the other one touches their screen. [/quote] It sounds like: There are two users. Each has their own device. On which they run your app. You want to display some UI… … that’s shared between the users… … so that user action on one device are immediately visible on the other device. Is that right? If so: What sort of devices? iOS devices? Macs? Or something else? How far apart are the users? Are you assuming that the users are close to each other? On the same Wi-Fi network? Or can the users be on different sides of the planet? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I was about to post a similar question, since I've been struggling with this exact issue for the last 3 days. The default app clip does not pop up when invoked from a QR code or NFC with a URL of the associated domain. I've read and re-read the docs (and re-watched all the app clip WWDC sessions) and they never directly address this. I'm suspecting that yes, Advanced App Clip Experiences are needed to use associated domains. The docs say: A default App Clip experience is required and can be invoked using Safari and Messages, as well as through an NFC tag, QR code, and links in other apps when using an Apple-provided App Clip link. Incredibly confusing. Why do Safari and Messages support the associated domain and not NFC or QR? And why not just say that in simple terms? I'd love for someone from Apple to confirm what the expected behavior is.

Offshore development can definitely be more affordable, but concerns about quality and communication are real. I’ve worked on quite a few outsourced projects, and the key is really about how you manage the process. Clear expectations, solid QA, and alignment go a long way. I recently wrote a post about common outsourcing mistakes and how to avoid them. If you're curious, you can find it by searching “mistakes in outsourcing software development site:nexadevs.com” on Google, it should pop right up. Hope that helps while you’re figuring out the best approach for your project!

I was referring to the official Apple documentation for the Speech framework, specifically: Asking Permission to Use Speech Recognition https://developer.apple.com/documentation/speech/asking-permission_to_use_speech_recognition Recognizing Speech in Live Audio https://developer.apple.com/documentation/speech/recognizing_speech_in_live_audio While these pages do not explicitly mention enabling the Speech Recognition capability in the Developer Portal, several other trusted sources — including community forums and prior Apple Developer Tech Support responses — have indicated that adding this capability in Xcode (which creates the com.apple.developer.speech entitlement) is required for full and stable functionality. If that is no longer the case, I would be deeply grateful for your clarification — especially since we are still experiencing permission issues and silence from the speech plugin in a properly configured app. Could you please help me with a way to set up speech on my app?

We need to be clear about terminology. You wrote: [quote='786048021, wangshibo, /thread/786048, /profile/wangshibo'] it was found that the app was forcefully quit by the system [/quote] Force quit isn’t really a term of iOS, but most folks use it to mean that the user removed the app from the multitasking UI by swiping up. That’s not what’s happening here. Rather, it sounds like: The user moved your app to the background. Shortly thereafter, the system suspended it. After a while the system starting running short on memory, and so it terminated your app. This is expected behaviour on most Apple platforms (everything except macOS). Your app is expected to handle it properly. [quote='786048021, wangshibo, /thread/786048, /profile/wangshibo'] subsequent operations could not be carried out. [/quote] Can you elaborate on what those operations were? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

A virtual device refers to the use of AudioServerPlugIn to create a nullAudio, similar to the open-source BlackHole. As you mentioned: for synchronized audio, the CoreAudio API AudioHardwareCreateAggregateDevice is used to create an aggregate device. I did this, and it was successful. However, when I switch the microphone mode to the voice enhancement mode, the number of input channels I retrieve from the aggregate device is incorrect. The specific issue can be seen in the following two help posts: https://stackoverflow.com/questions/79319480/mac-audio-software-aggregate-device-issue https://developer.apple.com/forums/thread/771690 Therefore, I had to abandon the aggregate device and use separate devices to capture and forward the audio. But this led to synchronization issues. @Systems Engineer

Please review the following document and sample to make sure you're doing all the right stuff for requesting permission to use speech recognition: Asking Permission to Use Speech Recognition Recognizing speech in live audio If that doesn't help and you're still getting a code signing error, maybe consider opening a code level support request so I can review your code settings. If you open a support request, please include a link to this thread so the request will be routed to me.

Hello, Can you please elaborate more on what you mean by virtual audio device? Traditionally if you want synchronized audio you'd need to use the CoreAudio API AudioHardwareCreateAggregateDevice to create an aggregate device, then you can assign this as the intended device for the AVAudioEngine.

This issue still exists in Xcode Version 16.3 (16E140). To fix the Audio Unit Extension App template to allow installation to an iOS device, you must reset these two Build Settings in the section Signing - App Sandbox : Enable App Sandbox Enable User Selected Files To reset, highlight the row and click delete. These build settings need to be reset for both targets: App target Audio Unit Extension target As Quinn mentions, if you want to deploy to the macOS App Store, you still need to enable App Sandbox. Go to the Signing and Capabilities tab > click + Capability > choose App Sandbox.

I tried to install the profiles, but they both seem to be the same profile - Facetime and Call Activity Logging Yeah, that's fine. What actually happens here is that at some point in the past we had different profile the included slightly different logging behavior but at some point the team decided to just consolidate on to one profile for everything. However, these profile are very widely used in very different context (for example, App Development vs. AppleCare), so it's easier to post the same profile with two names instead of trying to explain that one case should now use the other profile. actually, when checking crashes_and_spins there are crashes 20:01, 20:02 and 20:03... my bad Good. So, it sounds like the system side of this is working correctly. What is the recommended way to detect that we are launched before first unlock? So, my first and most important recommendation is that you NOT think about this issue in terms of any specific state. Yes, that's what's triggering the specific failure