build disappears

Thank you for your post. For help with the CarPlay , please post in the Apple Support Community. The Apple Developer Forums are for questions about APIs and features intended specifically for developers. https://discussions.apple.com/welcome If you are using a beta version of iOS (please provide the version and build) with CarPlay , please file bug reports through Feedback Assistant. https://feedbackassistant.apple.com/ Hope this helps and you find the solution quickly. Albert Pascual
  Worldwide Developer Relations.

OK, so this is the part I haven't explained as well as I should. You don't actually need to build the kernel, as you already have a development build of the kernel in the KDK. That's what kernel.development.t6020 and kernel.kasan.t6020 installed by the KDK in /System/Library/Kernels are That was it - I built a kext collection using this pre-shipped kernels in the KDK and I was then able to boot this custom kext collection without any issues. I used the kernel.development variant for my test. Upon boot I even verified that it was indeed using the development variant of the kernel: $> sysctl kern.osbuildconfig kern.osbuildconfig: development Thank you very much Kevin for this very valuable help. I have several other things to read and try out (including hopefully building a trivially modified kernel version from xnu sources and booting it), but this initial step had blocked me for several months to even think of these additional experiments. For now, I will just write up these step

Hello - For the situation you describe, the only possible mechanism for cancelling the subscription purchased in a TestFlight build using a production user account is to have your app call and present the App Store manage subscriptions sheet within the app itself, as documented here. Without that in-app capability, you must wait for the Sandbox subscription to cycle through its expected six (6) renewals before automatically cancelling, as documented here. If the Sandbox subscription purchased through your TestFlight app is not automatically cancelling after 6 renewals as expected, you can provide us with more details (the app name/id, a Sandbox transaction ID, etc.) and we can investigate further to see if the renewals and cancellations are not behaving as expected. Thank you.

Is there a better mechanism for this? We have been trying for 6 months to get an Enterprise Account - We have less than 100 employees, but we are contracting for a company that has a few thousand employees, who wants to MDM the app internally. The web pages to sign up keep kicking the application back, and every time we get an email from a person, it is obvious that no one is actually reading the application. The company we are contracting for logistical reasons CAN NOT USE TESTFLIGHT. They absolutely need it to be an enterprise build. Is there a better link than the one provided, because it’s very frustrating.

I filed a bug report (FB20465338) but I also want to note some more details here in case this is useful to someone: When navigating back/forward in a WebView or WKWebView, the page suddenly jumps up. The reason appears to be that WebKit automatically adds some padding to the top of the webpage to account for the unsafe nav bar area, but it then forgets to account for this padding when navigating back/forward. The effect is especially pronounced if you swipe back/forward. When swiping you see a static preview of the incoming page, but when you release the swipe, the page suddenly jumps up. As far as I can tell, this has always been an issue, but before iOS 26 it wasn't really a problem because the WebView would usually be flush against a solid nav bar. However, in iOS 26, this bug is problematic because Apple is asking us to flow the web content behind the nav bar; indeed, this is the default behavior of a WebView. There's effectively no good solution in iOS 26 because you basically have two choices: Adopt the

It will only work if you're building the app using Xcode 26. You also need to add the .icon file to your app. I was able to just drag and drop the file next to me assets bundle and it deployed it to my asset bundle in the next build.

[quote='860620022, dreisicht, /thread/802464?answerId=860620022#860620022, /profile/dreisicht'] the project is open source anyway. [/quote] Yeah, but if you send me a binary then I don’t have to mess around with build systems (-: [quote='860620022, dreisicht, /thread/802464?answerId=860620022#860620022, /profile/dreisicht'] Here is the zipped .app [/quote] Thank you! This layout is much what I’d expected: mach-o-images.txt Note I’m using the FindMachO.sh script from here. Or, as a hierarchy: hierarchy.txt That is, you have a vast array of code embedded within the Contents/Resources directory. It’s feasible to sign and distribute this. It doesn’t follow the rules in Placing content in a bundle, but this particular structure is tolerable, at least for the moment [1]. So, to sign this you need to generate a list of these code items, sort them in dependency order, and sign each one in that order. This is pretty much the process described in Creating distribution-signed code for macOS. Share and Enjoy — Q

@Engineer Hi Argun, Thanks for the follow-up. Behavior: On affected devices, DCAppAttestService.isSupported appears to be stuck false permanently (not intermittent). Current impact is small (~0.23%), but persistent for those users. Tried: We haven’t yet asked users to restart or delete & reinstall the app. We will do that next and report back. Devices: All affected devices are customer devices; we don’t have any of them on hand. Could you advise what remote logs would be most useful for you? For example: specific Console.app subsystems/keywords to capture (e.g., com.apple.devicecheck, DCAppAttestService), and whether a sysdiagnose from an affected device would help (and which components to focus on). If there are any known system/SEP conditions that can keep isSupported false until a DFU restore, please let us know so we can guide users appropriately. Happy to provide any additional app details you need (Bundle ID / Team ID / build type). Thanks again.