We're receiving crash reports where our app is killed by the system because of 0xdead10cc. If I understand correctly this is happening because our app has a file lock or SQLite database lock. Our app is using NSPersistentCloudKitContainer and is indexing the data to Core Spotlight. In my naiveté I assumed that NSPersistentCloudKitContainer and Core Spotlight would release any locks when app is suspended. What is the best way to solve this? Asking for more background time doesn't feel like a solution, that will just postpone the crash.

We're using a Transformable String array as an attribute in one of our Core Data entities. I saw that new this year is Composite Attributes, but this only seems to offer a dictionary. Right?

I'm playing around with Interactive Widgets and I am trying to make one that starts playing audio content without bringing the app to the foreground. The new Button used in interactive widgets accepts an AppIntent, but INPlayMediaIntent doesn't conform to AppIntent. Starting to play something directly from an AppIntent doesn't seem to work either. The system kills my process if I try to call the following from an AppIntent: ''' try! AVAudioSession.sharedInstance().setActive(true) '''

I have a view attachment attached to a hand anchor. When the attachment is facing away I don't want it to render. I might be missing something obvious, but I've made a System that runs on every render loop. In the update call I'm getting a reference to the Attachment using components. And this is as long as I got. I can't figure out how to get the normal of an Entity I receive in the update function. My plan was to take the head anchor normal and compare it to the entity normal. If they are facing each other I render the viewAttachment, otherwise not. Is there a simpler way? And if not, how do I get the normal of an entity?

Posted in the wrong subtopic, and I can't figure out how to delete this post.

Our watchOS App isn't opened when tapping on a Live Activity. Added the following to our Info.plist and still get the Open on iPhone option. <key>WKSupportsLiveActivityLaunchAttributeTypes</key> <array/> Is there something else we need to configure?

We have an iPad app and are using the new TabView and TabSection views in our sidebar. The TabSection is populated with data from a @FetchRequest that fetches data from CoreData. The data in CoreData is updated by a single worker that makes sure every value only exists once. This is done by using an OperationQueue with maxConcurrentOperationCount set to 1. This is crashing for our users, and we can't figure out why. We can't reproduce it, and it only seems to happen on iPadOS. We have the same code running on macOS and haven't received any reports. (We collect them all via 3rd party). The error is: NSInternalInconsistencyException Fatal: supplied item identifiers are not unique. Duplicate identifiers: {( ... )} Where ... is one to many comma separated strings. In our latest update we made sure the values are unique by passing them through a Set, unfortunately this is till crashing. Here's the fix we tried. var uniqueTags: [HashTag] { let set = Set(hashTags) let array = Array(set) return array.sorted { $0.name?.lowercased() ?? "" < $1.name?.lowercased() ?? "" } } We're out of ideas and have no idea what to do next.

Hello, In one of our apps we use DeviceActivityReportExtension to show the user how much screen time is remaining. The calculation is working as expected, but we have noticed that the labels in our ScreenTimeBriefReport are not localized to the device language. Example: Device with language set to Swedish App fully translated to English and Swedish Result: All labels in app are using the Swedish translations, except the strings in our ScreenTimeBriefReport instance. These labels are using the English localization. I've verified it's using the English localization from our Localizable.xcstrings file. I tried logging device language from our ScreenTimeBriefReport instance, but I could not see anything in Console.app. I guess this is intentional so no sensitive user information can be extracted. Is this a known feature or bug? If it's the latter, is there a known workaround? Sincerely, César

Hey, We're loading data from Core Data, and for some reason an error is thrown. This is happening extremely rarely and we haven't been able to reproduce it. The error thrown has the following description: Åtgärden kunde inte slutföras. (ScreenGenieCore.EnrolledView.(unknown context at $10087af4c).EnrolledError fel 0.) It is occurring in an app written in SwiftUI when the user taps a button. The managed object context is initiated in app init and provided to the view using the @environment modifier. So the viewContext should always exist. Still it throws an error saying unknown context .... Any guidance or possible things to investigate would be much appreciated.

Hey folks! In one of our apps we're using the FamilyControls framework to manage the screentime for the child. The app requires the Guardian to activate a subscription on his/her device to enable the functionality for the Child on the child device. We're currently using StoreKit 2 to get notified when there is an active subscription. The issue we're seeing (and our users) is that an activated subscription isn't instantly propagated to the Family members, in this case the device belonging to the child. Is this a known bug, and are the possible any workarounds? Currently we have to ask our users to "Restore Purchase" or wait minutes/hours for the app to active, which isn't a viable solution. We want it to "just work" :) Sincerely, César Pinto Castillo Ambi Studio

Playing around with the new TabViewBottomAccessoryPlacement API, but can't figure out how to update the value returned by @Environment(\.tabViewBottomAccessoryPlacement) var placement. I want to change this value programmatically, want it to be set to nil or .none on app start until user performs a specific action. (taps play on an item which creates an AVPlayer instance). Documentation I could find: https://developer.apple.com/documentation/SwiftUI/TabViewBottomAccessoryPlacement

Hey, We're crunching to get our products ready for the announcements next week but are being slowed down by Xcode Cloud. Builds are failing and are extremely slow. We're using the latest Xcode beta and latest macOS release so we can upload our builds continuously to TestFlight. We're seeing builds taking up to almost an hour, even though takes around 10-15 minutes when it doesn't fail. The errors we're seeing seem to be timeout, for example: Showing All Errors Only The step invocation hit a user timeout. The xcodebuild build invocation timed out. No activity has been detected on stdout, stderr or the result bundle in 30 minutes. Here are links to some builds which have been restarted multiple times but keep failing for reasons out of our control. Please advice on how to get unblocked. https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/8da12ae3-b454-4810-abe8-829f1af56a54 https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/ee7b1fae-1363-4265-9d64-692434b7ebf2 https://appstoreconnect.apple.com/teams/69a6de80-3540-47e3-e053-5b8c7c11a4d1/apps/1102236212/ci/groups/fd915140-db2c-4b3b-bff4-16939c22665a

Xcode 26 RC is not available on Xcode Cloud. This is a serious blocker affecting developers trying to be on App Store on day 1 of the OS 26 release. Is there an estimate when this can be in place?