“DTiPhoneSimulatorErrorDomain Code 2”

Thanks for posting the crash log. The stack you've shown isn't enough on its own to point at a specific cause — the WebKit frames are still , and there's no information about the WebView itself or what triggers the crash. Before going further, could you share the following? The WebView setup — how you create, configure, and present or dismiss the WebView. The relevant view controller code, your WKWebViewConfiguration, and the navigation flow that leads to the crash. Reproduction steps — what does someone do (or what does the app do) right before the crash? The frame _UIContextMenuAnimator performAllCompletions suggests a long-press preview menu may be involved. Does the crash require a context menu to have opened first? Frequency and conditions — does this happen in your own testing, or only in production via crash analytics? Specific iOS version (26.0, 26.1, 26.4)? Specific devices? Any particular network or content state? The original crash report, not a forwarded copy — those WebKit frames are us

Thanks for the focused reproducer and the video — they made this easy to investigate. There are two separate problems in what you're seeing, and the right answer is to switch to a different SwiftUI API for this kind of programmatic text editing. The bug in your code: String.Index invalidation after replaceSubrange RangeReplaceableCollection.replaceSubrange(_:with:) invalidates all indices into the collection (per the documentation), not just indices at or after the modified range. In your code: self.text.replaceSubrange(from..

@hydrudcatt3 Thanks for the post. The thread is 4 years old, I think will be a great idea if you could post a new thread with all the details of the issue and the code you have posted. Is what you experiencing like SwiftUI's implementation of .searchable sometimes holds onto the Binding longer than the view's lifecycle? Is that what you are seeing? Looking forward to see your new post with all the details. Albert
  Worldwide Developer Relations.

You've narrowed this down well, and the corroborating reply confirms it isn't device-specific. What you're describing isn't expected behavior — third-party MusicKit clients shouldn't lose access to playback because the native Apple Music app has a pending post-update onboarding modal. Shared service initialization (account readiness, subscription state, and so on) should happen independently of the native app's UI state, and the fact that a single Apple Music launch + modal dismiss restores everything to working order points to some shared component lazy-initializing only when Apple Music itself runs. A few things: On a force service initialization API: there isn't one in public MusicKit, and adding one wouldn't be the right fix — the underlying services shouldn't get into a broken state in the first place. That's the bug. Please file a Feedback Report. Even if other developers have already filed, duplicates matter — independent reports count as a signal of impact, so each FB from an affected app raises visib

We are also running into the same issues. Test broke in iOS 26.3 [SKTestSession] Error saving configuration file: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error clearing overrides: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error deleting all transactions: Error Domain=SKInternalErrorDomain Code=3 (null) [SKTestSession] Error setting value to 1 for identifier 2 for com.keepsafe.development.KeepSafe: Error Domain=SKInternalErrorDomain Code=3 (null)

Thank you for the post. Please check your SSL certificate as seems to have intermediate SSL errors. curl -v https://rob-auth.bankalbilad.com/.well-known/apple-app-site-association After you fix the SSL certificate you should read the Tech Note TN3155: Debugging universal links | Apple Developer Documentation#Use-universal-links-on-your-site {applinks:{details:[{appIDs:[2TK5X82C47.com.bankalbilad.NewRMB],components:[{/:/*,comment:}]}]}} As your AASA format is not correct neither. Look for an example of the AASA file. If you go over the troubleshooting and still have issues, I'd like you to submit a code-level support request so we can discuss this further privately. When you create the request, indicate that you were referred by Albert Pascual at Apple and make sure to include a link to this thread. Thanks Albert
  Worldwide Developer Relations.