“Popping Sound”

So the injection is finished right now, although I changed the container in singleton actor, that's the reason it won't affect anything. You assessment sounds about right. If your model container is a @State of the view, as shown in the API specification I linked above, and the view injects the container to a subview hierarchy, I'd expect that changing container triggers an update of the subview with the new container. So it's not possible to save the model data from another ModelContext to a new ModelContext, is that right? Right. If you save a model instance with a model context, and need to access the model instance from a second context, consider grabbing the persistentModelID of the instance and converting it to a new instance with the second context using model(for:). Best, —— Ziqiao Chen  Worldwide Developer Relations.

We are also seeing something similar running audio stem separation models on the GPU and have filed issues in feedback assistant, e.g. FB20777953. CPU and NPU inference appear unaffected.

Seeing the same issue on a couple of models we own - audio processing. Output diverges from 26.0.1 and 26.1. On our tests we have seen that a couple of models work as expected on CPU but present corrupt/degraded data on NPU/GPU. Would also like to know if Apple is aware of thjis issue as it is not only affecting our development but also our customer experience as our models are shared with clients and are used in production.

Hi Ziqiao, Your previous guidance to use a ModelActor and PersistentIdentifiers has successfully resolved all my data race crashes. However, I'm left with one persistent UI-level race condition, specifically related to deletion. My View Structure My setup is a standard master-detail pattern, which on iPhone (where I'm seeing this bug) acts like a NavigationStack: ScheduleView (Master): Uses @Query to fetch and display all events in a List. Each row is a NavigationLink. This view also has a swipe-to-delete action on its rows. EventDetailsView (Detail): The destination of the NavigationLink. It contains a Delete button. The Problem: A dismiss() vs. @Query Race When I tap the Delete button in EventDetailsView, I call my actor (e.g., await databaseManager.deleteEvent(id: event.persistentModelID)) and then immediately call dismiss() to pop the view. The Bug: When the app returns to ScheduleView, the row for the just-deleted event is still visibly active in the list for at least 5 seconds before it finally

It sounds like you’re building an accessory and you want to use Wi-Fi Aware to talk to that accessory from iOS. If so, go to Developer > Accessories, download Accessory Design Guidelines for Apple Devices, and review the Wi-Fi Aware chapter. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Creating bookmarks to the root directory of a volume was broken in earlier versions of 26. It looks like a change was made and that change broke NTFS. Good thing I haven't released yet. I need to double check. My workaround assumed that creating the bookmark would fail. I didn't anticipate success with invalid data. I don't know if my workaround would work for you. I have a special case where I don't actually need to access the data. I just want to know the URL. I can get the data I need without a security scoped bookmark. And it sounds like I need to re-do it anyway.

I'm having the same issue with a few of my PWAs. They work fine in Safari, but when installed as a homescreen app, audio playback won't start. It does work once if I restart the phone, but then stops working again if I close and reopen the app. Additionally, it seems that sequential playback doesn't work when the phone is locked. Instead of playing the next audio track, playback will stop until the app is re-focused, at which point playback will begin again.

Hmmm, that doesn’t sound right. While ExtensionKit on iOS has significant limitations, my understanding is that we do allow iOS apps to use extensions that are bundled within the app, and that’s what you’re trying to do. I’m gonna consult with Kevin about this and one of us will get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

We discovered the iOS version is not the culprit. All models starting with 14 series iPhones and onward are affected by this problem, even on iOS 17. Must be some glitched interaction of hardware and software feature. Affected models do not produce any audio, magnitude logging from C++ engine doesn't produce anything. static OSStatus mixerPlaybackCallack(void *inRefCon, AudioUnitRenderActionFlags *ioActionFlags, const AudioTimeStamp *inTimeStamp, UInt32 inBusNumber, UInt32 inNumberFrames, AudioBufferList *ioData) { AudioEngine *self = (AudioEngine*)inRefCon; uint32_t toget = inNumberFrames << 2; //printf(mixerPlaybackCallack: bus: %u, frames: %un, (uint32_t)inBusNumber, (uint32_t)inNumberFrames); if (inBusNumber < kMaxRemoteLines) { auto& audiobuffer = self->m_remoteBuffers[inBusNumber]; int32_t len = 0; if (uint8_t *buf = audiobuffer.tail(len)) { int32_t tocopy = len > toget ? toget : len; memcpy(ioData->mBuffers[0].mData, buf, tocopy); audiobuffer.consume(tocopy); if (tocopy &

Thanks. Oof. That is not good to hear. So presumably the only way out of this is if I hand the source code to my friend, they build effectively a new app with a new app id, new name on the store, new description, etc. They can take over from me with the new app, I can put something to that effect in my app description perhaps and remove my app from sale. Then existing customers who have downloaded it will still be able to use my version but all new people looking will go to his instead. Sounds like that's just about the only viable approach?

We have the same problem with iOS26 - thousands of crashes in the production. iOS 18 and older works just fine. We are not able to reproduce it locally. It started with building our app with xcode 26, with older xcode it woks ok even on iOS 26, but we were unable to do iOS 26 specific code. Fatal Exception: NSInvalidArgumentException +[_SwiftUILayerDelegate _screen]: unrecognized selector sent to class 0x1efa9da08 0 CoreFoundation 0xc98c8 __exceptionPreprocess 1 libobjc.A.dylib 0x317c4 objc_exception_throw 2 CoreFoundation 0x1656cc -[NSObject(NSObject) doesNotRecognizeSelector:] 3 CoreFoundation 0x464f8 ___forwarding___ 4 CoreFoundation 0x4e3a0 _CF_forwarding_prep_0 5 UIKitCore 0x18e7880 __35-[UIViewKeyframeAnimationState pop]_block_invoke 6 CoreFoundation 0x12170 __NSDICTIONARY_IS_CALLING_OUT_TO_A_BLOCK__ 7 CoreFoundation 0x1a47cc -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] 8 UIKitCore 0x18e76bc -[UIViewKeyframeAnimationState pop] 9 UIKitCore 0x1d0e8 +[UIViewAnimationS

This sounds like the issue being discussed here: https://developer.apple.com/forums/thread/803019 This has been fixed in macOS 26.1 which will likely be released today.

Same here for all audio tags!