dsym file

Well, that’s not good. I suggest you retry this on the current 26.3 beta, just in case. Assuming the problem shows up there as well, you should file a bug about it. Make sure to include a sysdiagnose log taken shortly after reproducing the problem, ideally as soon as you see the fuzzy screen you showed in your screenshot. Once you’re done, please post your bug number and I’ll take another look. At the API level, one option you have is to create an LAContext and pass it in to each SecItemCopyMatching call via kSecUseAuthenticationContext. It’s not clear whether you’re doing that or not. Please confirm either way. It’s also not clear if it’s even the right thing to do. This technique makes sense when the user performs a single high-level operation that requires multiple cryptographic operations with the same key. However, if the user performs two separate high-level operations back-to-back and that reproduces this issue, then trying to work around this using kSecUseAuthenticationContext isn’t really th

Hi @Vision Pro Engineer, thank you for your response. I followed the link you provided, and it worked! Thank you very much. ModelSortGroup is the solution. I won't be using ManipulationComponent because I need visionOS 2.0, but it's a very interesting component. That said, I encountered a problem with ModelSortGroup in my actual application, not the demo one (where my image comes from). I couldn't find any explanation, but using generateCollisionShapes(recursive: false) didn't work, whereas my spheres (which are real entities loaded from files) worked when I manually created the collision shape. I tried displaying the collision shapes using visionOS debugging, and both methods seemed to produce exactly the same collision shape, position, etc. Is there a logical explanation? Thanks for your help, it really solved my issue.

I have filed FB21917334 Thanks! however not in a Hypervisor Framework category as it does not exist Virtualization is fine. But that’s not a problem; it’ll find its way to the right place. ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK, cool. Well, not cool, but you know what I mean (-: Given that you can reproduce this so easily, I recommend that you file a bug about it now. When doing that: Make sure to enable additional VPN logging, per the VPN (Network Extension) instructions on our Bug Reporting > Profiles and Logs page. After reproducing the problem, grab a sysdiagnose and attach it to your bug report. Once you’re done, post your bug number here. My plan is then to grab the crash report from your sysdiagnose log and dig a bit deeper. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi Quinn, Thank you for above pointers. Following it, I found that: The release entitlements file we were using (Ro_ _ IOSS_ _ _n.entitlements) did not include com.apple.developer.payment-pass-provisioning, so the app never claimed it. That’s why App Store Connect flagged the entitlement as missing. **Fixes I made: ** a. Added this key (entitlement) to RoboIOSSiren.entitlements manually: com.apple.developer.payment-pass-provisioning and updated aps-environment to production aps-environment production b. After (a) I did below in order: Clean + Archive In Xcode: Product > Clean Build Folder… Then: Product > Archive Verify entitlements in the archive In Organizer, select the new archive → Distribute App → Custom → App Store Connect → Export On the “Review IPA content” screen, confirm the entitlements list now includes: com.apple.developer.payment-pass-provisioning Upload using Transporter Upload the exported .ipa with Transporter. Check App Store Connect Wait for processing and re-check the TestF

@thespoolapp, @Piergio, @pcasimiro10 , @thuat26 Please file a DTS code-level support for assistance. Be sure to include the following information: Version of Xcode and macOS used to build your app. Archive file containing your app and extensions. Information on whether you use a third-party tool to create your Xcode project. Sample Xcode project reproducing your issue. your Xcode project and the archive containing

Thanks for the post. I love crash files and you came to the correct place as they are better developers here that can help you with a crash. The interesting issue is that is crashing on swift core lib? However will be a great idea you follow this recommendations to post a crash file with all the information that can help them figure it out. Kindly submit a comprehensive crash report, adhering to the guidelines outlined in Posting a Crash Report. https://developer.apple.com/forums/thread/688669 Have you test it with iOS 26.2? In my modest opinion and without code nor much besides the header, the crash you're encountering, suggests that there might be an attempt to access memory that's either invalid or no longer valid. Ensure that the object or table or table items managing the isn't being deallocated prematurely. Any strong reference cycles or unintentional over-release could lead to accessing a dangling pointer. If the table view is being loaded from a storyboard or XIB, ensure there are no

Thanks for providing such a detailed report. Just to be sure that the testing environment on different devices is exactly the same: Does your app have an complication on the current watch face? In watchOS, you can expect that your app receives four background updates per hour if your app has an active complication, as mentioned here. The device's battery level is another important factor as well, so be sure your device has 80+% battery level when doing your tests. The behavior I described is on an app. It seems though that you are using HKObserverQuery + enableBackgroundDelivery in an App Extension, which has a quite different life cycle. Would you mind to share details about what extension you are working on, how you use HKObserverQuery + enableBackgroundDelivery in your app extension, and if the issue happens in an app on the same device as well. Other than that, given that the issue only occurs on a certain device, I think it's reasonable to start with filing a feedback report with a sysdiagnose f

For comparison, this command on my machine: nvram -p | grep boot-args Returns: boot-args debug=0x104c0c vm_compression_limit=4000000000 The debug entry is not required; that just happens to be how my machine is configured. Once the changes display correctly, the machine should behave according to these, and I run the test Python script aforementioned. Do you do anything different (besides the checks, of course, and the test script/language used)? Have you not been rebooting after you set the value? It looks like I wasn't entirely clear on this, but the boot-args values are quite literally the arguments passed into the kernel when it boots up. Many of them, including this one, are used to set critical constants that are then used to define the system’s wider behavior, often in ways that simply cannot be dynamically modified. At a purely technical level, I'm not sure ANY of them actually apply dynamically; in general, the system relationship to pre-boot state (like firmware variables) is that they're pushed int

So far I've been unable to reproduce the problem you are seeing. Would you be able to make a reproducer project and file a feedback with it attached? If you do please reply back here with the feedback ID so I can make sure it gets to the right team asap.

Here are some debug tips we've seen work best, in order of what to try first: Make sure your macOS, Xcode, and other operating systems you're developing for all are on the exact same version >= 26.0. It's most important that Xcode and Mac have the same exact version number, since these asset issues typically arise from version mismatches. Settings > turn Apple Intelligence off > restart your Mac > turn Apple Intelligence back on to trigger re-download of assets Settings > make sure Siri is turned on and Apple Intelligence is turned on to ensure all assets are downloaded If all else fails, kindly file a feedback report and include all of your OS and Xcode version numbers, so we can debug your issue.

Thanks for your post and interesting on your comment about: Long press on the Safari icon and choose Remove app If you make the system avoid using Universal Links by telling how to handle the link. Since you mentioned universal links, make sure there's no conflict with any custom URL schemes defined in your app's . Universal links should ideally not interfere with opening URLs in a browser unless specifically set up to redirect to an app. 
Since you observed different behavior on iOS 26.0+, double-check whether this is related to a beta version or a specific OS bug. Review Apple's release notes or beta forums for any related issues and consider filing a bug report if necessary. Ensure you're testing on various devices and simulators, as sometimes configuration or environment-specific issues can cause unexpected behavior. But I’m wondering if you are disabling the link itself, you can see that on the swctutils file search for the link itself inside that file. Can you publish the resu