I just made a small test app that uses SwiftData with CloudKit capability. I created a simple Book model as seen below. It looks like enums and structs when used with CloudKit capability all trigger this error: 'NSKeyedUnarchiveFromData' should not be used to for un-archiving and will be removed in a future release I fixed the error by using genreRaw String and using a computed property to use it in the app, but it popped back up after adding the ReadingProgress struct Should I ignore the error and assume Apple still supports enums and codable structs when using SwiftData with CloudKit? import SwiftData @Model class Book { var title: String = var author: String = var genreRaw: String = Genre.fantasy.rawValue var review: String = var rating: Int = 3 var progress: ReadingProgress? var genre: Genre { get { Genre(rawValue: genreRaw) ?? Genre.fantasy } set { genreRaw = newValue.rawValue } } init(title: String, author: String, genre: Genre, review: String, rating: Int, progress: ReadingProgress? = nil)
Search results for
Popping Sound
19,345 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Greetings, With MacOS 15 Sequoia, Apple updated key-value-observations in such a way, that an unremoved observation by a now deallocated object will no longer cause an exception, when the observed object triggers said observation. While this is fundamentally a positive change, the issue comes with the fact, that this change affects systems based on the version of their operating system and not the version of the operating system of the build system. Many of our customers use old operating system versions and old hardware - meaning they can't easily update. Since we need to use up to date Xcode versions to develop for newer systems, our developers tend to have rather new OS versions. This means, that we are increasingly facing bugs which only happen in customer systems but not in most developer (or QA) systems. Currently, we still can use earlier OS versions with Xcode to fix these bugs, but once the used Xcode versions no longer support MacOS 14 or below this will become a major hurdle. Are there known soluti
I am using AlarmKit to schedule alarms in an app I am working on, however my scheduled alarms only show up on the lock screen. If I am on the home screen or elsewhere I only hear the sound of the alarm, but no UI shows up. Environment: iOS 26 beta 3 Xcode 26 beta 3
Topic:
UI Frameworks
SubTopic:
SwiftUI
This can be reproduced from scratch in just 2 minutes: create a brand new iOS app and give it the push notification capability. Change the app delegate template code to this: @main class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate { func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool { UNUserNotificationCenter.current().delegate = self // UNUserNotificationCenter.current().requestAuthorization(options: [.alert, .badge, .sound]) { granted, error in // NSLog(Notification permission granted: (granted)) // DispatchQueue.main.async { application.registerForRemoteNotifications() // } // } NSLog(didFinishLaunchingWithOptions returning) return true } // Called when an APNS token has been sucessfully obtained func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) { let token = deviceToken.map { String(format: %02.2hhx, $0)
Topic:
App & System Services
SubTopic:
Notifications
Tags:
Hello, thank you for your response. I have a PDF with form field values. The PDF is essentially always the same, but the field values differ. Here is an image from the PDF. Date: for example, is always the same. To the right of it, the current date is placed as a form field value. As I hover my mouse over the date, the blue rectangle behind it appears indicating it's a field value and that it's somehow not baked into the PDF. I don't know that this is considered an annotation? After I have opened the PDF in Preview (a contract in this example) I attempt to annotate it by signing it with my digital signature by overlaying the signature block of the contract with a PNG file of my digital signature. When I attempt to annotate it, it says the PDF Is password protected (I assume that my ability to edit the actual date of 9/7/25 and other field values is why it's locked--which is fine--I don't want to edit existing values). But because the PDF is locked, I can't, for example, create an automation which annotates th
Topic:
App & System Services
SubTopic:
Automation & Scripting
Tags:
On the latest Xcode beta 7, and iOS Beta 9 I cannot get the custom alarm sound to work no matter what I try. I have tried in the simulator and on a physical device. The my-sound variable points to a local file in the project, and I’ve confirmed that Bundle.main can locate it. What am I doing wrong? import Foundation import AlarmKit import SwiftUI struct DefaultAlarmMetadata: AlarmMetadata { let label: String } struct DoesNotWork: View { public func buildAlarmConfiguration() async throws -> AlarmManager.AlarmConfiguration { let stopButton = AlarmButton(text: Stop, textColor: .red, systemImageName: stop.circle) let alertContent = AlarmPresentation.Alert( title: Mocked Alarm, stopButton: stopButton ) let presentation = AlarmPresentation(alert: alertContent) let metadata = DefaultAlarmMetadata( label: My Mocked Label ) if let soundPath = Bundle.main.path(forResource: my-sound, ofType: caf) { print(Sound file found at: (soundPath)) } else { print(Sound file not found
Topic:
App & System Services
SubTopic:
Notifications
When setting a custom sound in AlarmKit, the alarm only plays the audio file once. I can understand why push notifications would play a sound only once, but I don’t understand why alarms can only play the sound for less than 30 seconds. We’re already at beta 6, so I’m wondering if Apple still hasn’t fixed this or if they have no intention of fixing it.
Topic:
App & System Services
SubTopic:
Notifications
Hello @Crixoule ! Hope this will be in VisionOS 26. Yes! In visionOS 26 we introduced attach(_ to:), which is the new, recommended way to attach an Entity to a GeometricPin on another Entity. So in your case, it sounds like you'd be calling attach on the entity you want to attach to Mesh01, and then pass in the Mesh01 entity as a parameter. I then need to manually add all the animations to the first file so I can build the library. Would be cool if the USD file could read the animation strips (NLA) and combining all animations in separate slots for RCP. I strongly recommend sending feedback about RealityKit's animation API including details of your use case using Feedback Assistant. I agree with you that the process of sequencing all your animations in Blender's NLA and then splitting them up in RCP with the AnimationLibraryComponent can be awkward, and your feedback and use case will help us improve this experience in the future.
Topic:
Spatial Computing
SubTopic:
Reality Composer Pro
Tags:
As you suggested,we have now initialised PushKit on the main queue. We are currently monitoring the issue since it is not consistently reproducible. Note that my concern here isn't really about using threads, it's about creating unnecessary race conditions. In concrete terms, it's common for a PushKit delegate to assume its CXProvider target exists (so it can call reportNewIncomingCallWithUUID), but if initialization is happening on a different thread, it could be possible for the PushKit initialization to get ahead, so the PushKit delegate fires before you've finished initializing CallKit. You can eliminate any possibility of that by following some simple guidelines: Use the same thread for CallKit and PushKit. I normally recommend the main thread, but that doesn't actually matter. Set up CallKit and PushKit on the same thread you'll use for the delegate and initialize all of them at the same time. This ensures that none of your delegates can fire until everything has been created. Set up CallKit first, then
Topic:
App & System Services
SubTopic:
General
Tags:
Hello, I’m building an iOS application that supports peer-to-peer file transfer. My goal is to use the WebRTC data channel only (no audio or video) to send files between users. I understand from Apple’s documentation that: • Apps are generally suspended in the background, and arbitrary sockets (like WebRTC) do not continue running. • Background file transfer is officially supported via URLSessionConfiguration.background, which the system manages reliably even if the app is suspended or terminated. • VoIP use cases require CallKit + audio/VoIP background modes, and CallKit must be used for legitimate calls (audio/video). What I want to confirm is: Is it supported for a WebRTC peer connection using only the data channel (no audio/video track, no CallKit call) to continue sending data when the app is in the background or locked? I considered using BGProcessingTask and BGAppRefreshTask, but as far as I can tell, those don’t allow maintaining long-lived sockets for active data t
I am trying to debug the AAX version of my plugin (MIDI effect) on Pro Tools, but I am getting the following error (Mac console) when attempting to load it: dlsym cannot find symbol g_dwILResult in CFBundle etc.. I used Xcode 16.4 to build the plugin. Has anybody come across the same or a similar message? Best, Achillefs Axart Labs
So, first terminology: Your Team ID is a 10 character code that identifies your team. For example, SKMME9E2Y8 is my individual Team ID. A bundle ID uniquely identifies your app, typically using reverse DNS notation. For example, com.example.test798928. An App ID is a bundle ID combined with an App ID prefix. For example, SKMME9E2Y8.com.example.test798928. An App ID prefix is either your Team ID or a unique App ID prefix. A unique App ID prefix is a 10 character code that’s allocated to your team, different from your Team ID. For example, one of my teams is allocated the App ID prefix of VYRRC68ZE6. App ID prefixes are effectively deprecated. If you previously used a unique App ID prefix for your app, you should be able to continue to use that same App ID prefix. Where is no requirement to migrate to using your Team ID [1]. Which brings us to this: [quote='799483021, ming2, /thread/799483, /profile/ming2'] But I cannot update it anymore because its AppID that appears in my account … is PREFIX_NEW(team ID).com.
Topic:
App Store Distribution & Marketing
SubTopic:
General
Tags:
You say half the features no longer work, which means the app still has some features that do work. You might have customers using those features, and if they don't require any services from your company and its servers then they can be left alone as they are. Or, you could update the app and slim it down so it contains only the features that still work. Yes, I see your app developer has left, but you can easily hire a short-term contractor to update your app to do this. You would also be able to pop up a splash screen explaining the changes. Most people have automatic app updates enabled so most of your users will be caught by this. This route would be a cleaner way to handle things, as the app wouldn't show features that don't work anymore, and users wouldn't have to skip round them while using the app. I guess it depends on whether you want to be nice to your existing customers, or don't really care. (I don't mean that in a bad way!)
Topic:
App Store Distribution & Marketing
SubTopic:
General
With the correct corner radius changing in iOS 26, I wondered if there is a way to get properly rounded corners inside containers like sheets without hard-coding a constant value. Here's the results of some experiments I did, example code below. The new in Beta 4 ConcentricRectangle seems nice. Notable here is that it doesn't pick up the larger corner radii from the device corners: If you want all the corners rounded, the isUniform parameter of ConcentricRectangle seems helpful. It doesn't apply the corners in a View in the middle though, not sure if this is an oversight or if this has some purpose: ContainerRelativeShape looks ... interesting ... as of Beta 4, with the larger bottom corners rounded according to the device corners, but the actual bottom corners not fitting the device corners. With ContainerRelativeShape one can also get the middle part to have proper rounded corners in this example ... if you set the outer .containerShape(RoundedRectangle(cornerRadius: 36)) yourself. Notable here is that it t
Topic:
UI Frameworks
SubTopic:
SwiftUI
I just found that you can just log in with your snadbox account when the login request is popped up in your app which has a in-app purchase. Then you also can find sanbbox account menu in the Settings > Users and Account. For just a record.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags: