dsym file

Turns out this is not a feature at this time. Filed a Radar: FB21986015

Thank you for providing this and uploading the file so that the team can review it. Let’s allow them some time to examine the trace file and determine the cause of the issue. I recommend that you monitor the Feedback Assistance correspondence in case they have any questions or suggestions. For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.

[quote='876405022, Pushpak-Ambadkar123, /thread/815498?answerId=876405022#876405022, /profile/Pushpak-Ambadkar123'] can we show any kind of custom error or alert when user tries to open blocked URL in case of URL Filter network ? [/quote] In the URL filter architecture your code isn’t the one making the actual decisions. Rather, your code sets up the filter’s state and the system applies that filter. So your code doesn’t run on the per-URL path and thus can’t do anything on that path. WWDC 2025 Session 234 Filter and tunnel network traffic with NetworkExtension talks more about this and I encourage you to watch it. So, your question is actually “Can we configure the filter to show a custom error?” And AFAICT the answer to that is “No.” However, I think it’d be reasonable for you to file an enhancement request for such a configuration option. If you do file an ER, post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail

Thanks for checking this. And I’m glad to hear that things are improving. [quote='876543022, TChrist, /thread/813973?answerId=876543022#876543022, /profile/TChrist'] We will provide a leaks report … from the 26.4 device in the Feedback. [/quote] Thanks. Although I think you might be better off creating a new bug for that. The current bugs were used to track the fix for the major memory issue that landed in 26.4 beta. The remaining minor leak is likely to have a different cause and thus it’s better to have a different bug. If you do file a new bug, please post its bug number here, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thank you for your guidance! Unfortunately, we have been unable to reproduce the crash internally, and it does not appear in Xcode Organizer. All occurrences were reported from production devices, so we do not have access to the corresponding .ips files. However, we can provide the full stack trace from Firebase Crashlytics if that would be helpful. a79d64a106f9d569e54661f0c2e361fd_crash_session_140bafc49a6e4ef487d22d01806fc1b7_DNE_0_v2_stacktrace.txt a79d64a106f9d569e54661f0c2e361fd_crash_session_ea0e80b874de47bdb671e7b530afa446_DNE_0_v2_stacktrace.txt

For what it's worth, I filed another feedback report (https://feedbackassistant.apple.com/feedback/21980712) with Apple, with as simple an example as I could craft.

(2) Redesign your approach such that you stop actually doing any “long-term running. That's a no-go. Jobs just have to run until they are done. There are dozens if not hundreds of pieces of data that are built and used along the way. Some of them are hogs that will run for 3 hours. How isolated are each of these jobs? For example, is progress being routed back to another thread or is all of the work contained to that thread? All the work for each job is pretty much self-contained in its thread as far as the SBApplication goes. Each job gathers data from the network, generates one of more InDesign documents and saved the resulting files of various types. They all communicate back to other servers by various means (simple I'm still working heartbeats), communicate with main parent app and various objects in the app to show progress, all of which has been heavily stressed and show no signs of causing problems. Swift has wormed its way into this fairly old Cocoa app, mostly in the data access from networ

Hi, thanks for posting this — I've been hitting the exact same wall. I'm building a screen time management app and spent considerable time trying to persist per-app usage data from the DeviceActivityReportExtension to the App Group container. I exhaustively tested every storage mechanism available: Core Data, JSON files, UserDefaults (App Group suite), Keychain, raw POSIX syscalls, SQLite, iCloud KV, and NSUbiquitousKeyValueStore. All fail with permission errors — the extension is completely write-locked at the kernel level (POSIX errno 1 / EPERM). I also confirmed the DeviceActivityMonitor extension has the same restriction. So I'm very interested in your finding that the host app can reconstruct raw activity data from the report. Could you share more about the technique you used? Specifically: How does your host app access the data from the report extension? Is it through the rendered view hierarchy, some callback mechanism, or something else entirely? Are you able to get per-app bundle identifiers

That's interesting about the difference between NSOperation and NSThread as far as Mach ports go. I watched the # ports in Activity Monitor as I ran a job, and it certainly doesn't climb as each job runs. It goes from initially in the 300s to the low 500s right when the job starts, and stays around there, even after the job ends, and then I run the same job 2 few more times without quitting. This app can run for days or weeks. It can process anywhere from a few to probably a couple hundred jobs a day. Yes, each job creates a new NSOperation and a new SBApplication, which are both destroyed when each job finishes. Each job can call into the SBApplication hundreds or thousands of times. The rate at which each script is run can be as fast as possible, given the speed at which InDesignServer will process each script. At times there is barely any application code going on between each script. (E.g. ask InDesign for the range of some text, tell InDesign to do something with that range of text, tell InDesign to repl

Thanks for the post, my guess here is your process is called KSCrash? The crash file should be posted as an attachment to be able to analyze. Kindly submit a comprehensive crash report, adhering to the guidelines outlined in Posting a Crash Report. https://developer.apple.com/forums/thread/688669 As you said, the error typically indicates that your application is trying to access memory that has already been deallocated or is otherwise invalid. Although you mentioned using Address Sanitizer, double-check your configuration to ensure it's correctly enabled. Sometimes, specific project settings might prevent tools from working as expected. If you're using collections that hold objects, ensure they are not being modified. Use or breakpoints to trace object lifetimes and ensure they are being deallocated when expected. This can help pinpoint where the object is being released prematurely. If you're using third-party libraries, ensure they are up-to-date, as bugs in libraries can manifest similarly. Howev

There have been some behavioral changes on N1 chip devices; especially in areas where the BT spec has not had a single way of interpreting things. We have been observing these changes and changing them back if appropriate and are considered regressions. So, the first thing you should do is to test all this in the latest iOS 26.3 and see if anything has changed from your earlier observations. Also, there would have been some changes on patterns of use that were never meant to work, but just happened to work, and those would have been corrected. For example, scanning without services is not supposed to work, and was never expected to work in the background. If you are scanning in the background without services, and whatever the Flutter library may have been doing to work around that limitation (if anything), and that has stopped working, you can consider that a bug that has been fixed. Similarly, advertising packets in the background have always been on a best effort basis. Also, it has always been possible th

Our SSH certificates are in OpenSSH format (RFC 4253), not X.509. These use a custom binary encoding that SecCertificate doesn't understand. Since kSecClassCertificate expects X.509 DER format: Should we store OpenSSH certificates as kSecClassGenericPassword with descriptive metadata? Is there any Keychain support for non-X.509 certificate formats? Or is the recommendation to keep them as files and only move X.509 TLS certs to Keychain? Example OpenSSH Certificate (text format): ssh-ed25519-cert-v01@openssh.com AAAAIHNzaC1lZDI1NTE5LWNlcnQt... Our current thinking is to store these as generic passwords: let query: [String: Any] = [ kSecClass: kSecClassGenericPassword, kSecAttrService: com.teleport.ssh.cert, kSecAttrAccount: (cluster).(user), kSecAttrLabel: Teleport SSH Certificate, kSecValueData: sshCertData, kSecAttrAccessible: kSecAttrAccessibleWhenUnlockedThisDeviceOnly ] Is this an acceptable approach for non-X.509 certificates?