build disappears

Could you share your understanding of the crash and give any hints on how we can fix it? So, let me actually start by commenting on this: At first, we assumed that the issue is with hardware. The first thing to understand here is that DEXTs are FULLY capable of panicking the kernel and probably always will be, particularly PCI DEXTs. The main benefit DEXTs provide is that they DRAMATICALLY improve overall system security and risk by constraining the range of what it's POSSIBLE for a component to do. Your DEXT only has access to a very limited set of kernel data, so that's the ONLY kernel data your DEXT interacts with. It's possible for a network DEXT to disrupt the network stack, but it's very difficult to see how it would disrupt the file system. However, your DEXT is still being given access to many of the same resources it would have access to as a KEXT, and many of those resources are inherently dangerous. In the case of the PCI family, that issue is quite direct— I don't know of any way to build

Issue still in iOS 26.0.1 Reproduce with the sample app 'DiffableDataSourceSample' from https://developer.apple.com/documentation/uikit/updating-collection-views-using-diffable-data-sources. It runs with UISplitViewController columns populated when compiled for target iOS 18.2. It comes up empty when target is changed to iOS 26. Both builds run on iPad at iOS 26.0.1 My app was patterned on this sample app and is failing to show content in the same way. FB20611981 submitted

Yeah! It's working! I have a macOS 26.0 host. In UTM I have a macOS 15.7 guest with a Provisioning UUID that has never been added as a device in the developer portal. In my developer account I added a new device with the guest VM's UUID. It's the longer style with lowercase hex digits. I then edited my existing manual provisioning profile with the new device. In Xcode (26.1 beta 2) I changed my app's signing from automatic to manual and referenced the updated provisioning profile. I built the app and copied the new app to a share I use for the VM. I ran the VM and tried to run the updated app. It failed. I missed one step that maybe some others might miss. In Xcode, go to Settings, Apple Accounts. Select your account. Then select your team. Then click on Download Manual Profiles. Once I did that, I rebuilt the app with the now properly updated provisioning profile and recopied the app to the share. And now the app runs in the guest VM! Key steps for those that are not starting from scratch: You need a VM with

You can either press the button, or press the return key on the keyboard. In both cases the keyboard abruptly disappears on both the simulator and iPhone 17 pro. Here's a video from the simulator: https://www.dropbox.com/scl/fi/8qc7is8iqpcjigta71qbq/keyboarddismissal.mov?rlkey=ftgnuoiu4x6mc8qokh5xw22b1&st=bpqb26b8&dl=0 I see others reporting similar issues here: https://github.com/facebook/react-native/issues/53626

I was able to test on my own, and in my tests it seems like provisioning profiles now work in the VM. But it took some extra work than just recreating the provisioning profile. My host is on macOS 15.7.1 (24G231). tl;dr try making a brand new VM such that it has a new provisioning UDID and try again My success case was as follows: I had an older clean install VM on macOS 15.7, but it does have the newer provisioning UDID style. I did not add it to my account until just now, however. I manually added the provisioning UDID to my devices list on the developer website. Now, the new device that I just registered on the website has an identifier with lowercase letters (e.g. c28165661eb...) (before, it looks like it automatically set it to uppercase). I recreated the provisioning profile, and built an app using Xcode on my host. I transferred the built app into the VM via a shared folder. I opened the app, and the app extension worked successfully (in my case, my app itself doesn't use a provisioning profile, but it

Hi Emmanuel, Thank you for your response. I have reviewed the section you pointed out and did some changes. 1.Overriden prefersInterfaceOrientationLocked to return true 2. Implemented didUpdateEffectiveGeometry callback to force the layout After this I am seeing two issues After the presentation and dismiss UI is flickering. Looks like there is some animation happening but not sure what it is. This happens only on device and not observed in simulator. In landscape the safearea position is coming same as portrait. I have uploaded sample project here https://limewire.com/d/n3ioq#sc6PR1GkiG. Can you please have a look and help in fixing this? Steps to reproduce Build and run app in xcode 26 and iOS 26 device Select any row and observe the detail view presentation Select Back button and observe the presented view controller Thanks Harsha

I found a bug when building with Xcode 26.0+. The system incorrectly assumes the TabBar is hidden on app startup, which causes a layout issue until the first device rotation. Workaround: In your target's Build Settings, set Status Bar Initially Hidden to NO. Also note that the UIStatusBarHidden key in your project's Info.plist directly controls the initial status bar visibility.