Popping Sound

You can use the isReadable value from URLResourceValues. However, it sounds like you're not approaching this from the right direction. You should never need to do this in the first place. Your app shouldn't attempt to read random files. It should only attempt to access files that the user has specifically requested. And even then, you shouldn't check readability. That's not reliable. Instead, just try to do what the user asked and report an error if it fails.

This definitely sounds like a bug. Can you please file a Feedback Assistant bug report to Foundation Models Framework so we can take a look at your Mac's and Xcode's system state? In the meantime, here are a few tactics that might help reset whatever's gone wrong: Close Xcode. Restart your Mac. Open Xcode. If that doesn't work: Go to Settings -> Apple Intelligence & Siri -> turn Apple Intelligence off. Restart your Mac. Then turn Apple Intelligence back on.

During testing, we noticed that if the user backgrounds the app (still connected to the device’s Wi‑Fi) and opens Safari, the extension’s stop is invoked with NEProviderStopReason.unrecoverableNetworkChange / noNetworkAvailable, and iOS tears the extension down. What's the specific testing scenario here? More specifically, is this real world testing with a disconnected device or is this a development device that's attached to a Mac, particularly with any kind of “active” interactions between the device being tested and the Mac? The one scenario I can think of that might explain this is that Safari has its own network-based debugging infrastructure, and it's (theoretically) possible that might be disrupting the app’s normal networking behavior. Related to that point, are you SURE the device is on the same WiFi network? I can't think of any scenario where NEAppPushProvider would stop working while you remained on the same network, but I can see the device changing networks without that being obvious. What I'd a

I've had this exact issue pop up occasionally as well. Our issues have been a combination of this and what I've posted in this thread: https://developer.apple.com/forums/thread/806242

Hello @psqv , thank you for your question! Can you share more about what exactly you're trying to do? I want to make sure I understand correctly so the answer I give is useful. The first thing that may be going wrong is that you say you are sampling the Image using Image(float), which only gives you one channel, and then multiplying that with a Color3f. I suspect you need to modify the Image node to be Image (Color3f) as well. You can set this in the inspector for the node in Reality Composer Pro. Your description of your baked lighting setup sounds unusual to me. It sounds like you are trying to multiply the color of two textures together in the same material. This should be possible (the sampling mode on your image node might be causing it to break), however I don't think this is the correct way to handle baked lighting. Baked lighting only needs one texture, your base color texture, that already contains all your shadows and highlights. Ultimately, your baked lighting shader graph should

FB20985796 (Issues Handling Multiple Incoming Calls in CallKit) Perfect, thank you. I filed a bug in Feedback Assistant. Is there another way to file a bug to get a faster resolution? No, not really. In this particular case, I think you should plan on working around the issue instead of waiting for the system to address this. This is a VERY longstanding issue (I suspect it's basically always done this), which makes it hard to justify as a high-priority fix. In terms of working around this, two tools I'd highlight here: The direct workaround is to put your active call on hold before you report the next call. In case you're not aware, you can safely hide new call reports while on an active call by reporting your new call using the same UUID as your currently active call. If your call is still active, you'll get CXErrorCodeIncomingCallErrorCallUUIDAlreadyExists (which you can ignore). If the existing call has ended (this can happen due to communication race conditions in the call infrastructure), then you'll get

Hi @VaiStardom I can confirm SpatialTapGesture doesn't consistently register direct input (trigger callbacks) on entities outside a person's field of view. However, you can use hand tracking to create a custom gesture that works on all entities, regardless of their position, as long as visionOS can track the person's hands. This approach only works within an ImmersiveSpace and requires adding an NSHandsTrackingUsageDescription entry to your app's Info.plist that explains why your app needs hand tracking access. The code snippet below demonstrates this technique by playing a sound when a person taps a cube, even when it's outside their field of view. import RealityKit import SwiftUI import AudioToolbox struct ImmersiveView: View { @State var spatialTrackingSession = SpatialTrackingSession() @State var collisionEventSubscription: EventSubscription? var body: some View { RealityView { content in let cube = ModelEntity( mesh: .generateBox(size: 0.1), materials: [SimpleMaterial(color: .green, isMetallic:

Thanks for filing FB20975128. While we investigate, I suggest switching your buttons to AppKit types as a workaround. It sounds like you're using SwiftUI to share the callout code between macOS and iOS, so I realize the impact of using platform-specific code here, but that will at least give you a path forward while this is investigated. — Ed Ford,  DTS Engineer

The decision of whether the filtering entitlement is granted or not is solely in the hands of the entitlements team. Nobody here will have any involvement in granting or expediting the request. If you feel like the filtering entitlement is something you cannot live without, you would need to make your case to the entitlements team. That said, use of reportNewIncomingVoIPPushPayload() does not depend on the filtering entitlement. The filtering entitlement is only required to make the notification silent. You can still use the functionality of converting notifications to VoIP calls, although the notification will be visible. By adapting your messaging in the notification (using the extension) to something that explains the situation and changing the interruption-level key in the payload to passive, so the notification will not interrupt a foreground app, or make a sound or light up the screen in most cases (while still being visible, though), you should be able to implement the functionality you are af

My example above is contrived, but rather than having environment values for .name, .age and .address it sounds like I should just have .person, which is an @Observable object containing the three properties. That way, writes to any of those properties don't trigger the issue you were talking about in the video. You could also just use @Environment(Person.self) private var person instead of a key, and inject it with .environment(person). However, in your example, since those environment variables wouldn't likely update very frequently (they're not really in a hot path) the cost of putting them in the environment is probably negligible. In my demo, it really adds up because the environment is basically being updated on every single frame. I wouldn't say that you need to go back to all your uses of environment values and change them to use @Observable classes, but if you're seeing performance issues, or building something new, it's worth considering.

Sounds like the classic off-by one error to me. PDF Pages are traditionally one-based, while many functions in PDFKit, i.e. page(at:) are zero based. https://developer.apple.com/documentation/pdfkit/pdfdocument/page(at:)