“Popping Sound”

So, let me start with the causes of these failures: But when I do, the signing certificate status in Xcode shows as failed. Why is that? This post has more detail, but in basic terms, your app’s signing is created from two components: Your Entitlement.plist -> This is used to create the actual code-signature attached to your app bundle. The provisioning profile -> This is a file that we've signed and which is then embedded inside your app’s bundle. (Note: not all signed apps have/need one of these, but all DEXT do). The system validates the entitlement by comparing the entitlement values contained in those two files (your app’s code signature and its embedded provisioning profile). That's why the profile (#2) is signed by us - it proves we want your app to have the entitlement. Xcode checks that your app is properly signed by comparing the data in those values to ensure that they match, creating this failure when they don't match. What I wanted to convey in my previous post was that I think I should inc

@Etresoft You can use the isReadable value from URLResourceValues. Thank you. This is exactly the API I was looking for. However, it sounds like you're not approaching this from the right direction. I'm not trying to open random files...; I just want to use it to prompt the user to obtain access permissions if they don't have them for the file they tried to open (the file linked by an alias).

This sounds like a regression our engineering teams need to investigate this issue, as this might indicate an issue with iOS 26.x We'd greatly appreciate it if you could open a bug report, include any logs and sample code or models that reproduce the issue, and post the FB number here once you do. We would also like a diagnostic log. It would be very helpful if you could please go to https://developer.apple.com/bug-reporting/profiles-and-logs/ and follow the instructions for Location Services for iOS to install a logging profile on your device. Then reproduce the issue, and follow the instructions at the above link to create a sysdiagnose. And attach that to the Feedback report as well. Bug Reporting: How and Why? has tips on creating a successful bug report. Important: For feedback related to a specific framework or API, select Developer Technologies & SDKs as your Topic, then select the specific technology and relevant OS. For feedback related to Xcode, App Store Connect, or other developer too

I apologize For the typing mess ups I just was wondering if core audio could be used as an audio device? so I can record my audio inputs in my internal audio for Mac?

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