Search results for

build disappears

49,448 results found

Post

Replies

Boosts

Views

Activity

Reply to Metal fails to create PSO on AMD based GPUs
Hello, Pre documentation Metal libraries built using Metal shader converter tools require a device that supports Argument Buffers Tier 2, running macOS 14 Sonoma, iOS 17 or later. If you build a Metal library for earlier OS versions, not all features will be supported. AMD GPUs lack many of the features offered by Apple Silicon and consequently PSOs won't compile (irrespective of Metal Shader Converter). Check the Metal Feature Set Tables for details.
Topic: Graphics & Games SubTopic: Metal Tags:
Sep ’25
Reply to Instructions for debugging recent macos kernel versions?
Hello Kevin, uname -v on my local system shows: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:30 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6020 so I've been using T6020 as the platform when building the kernel. The corresponding xnu source is this tag https://github.com/apple-oss-distributions/xnu/tree/xnu-11417.140.69 and the KDK is KDK_15.6_24G84.kdk. sw_vers shows me: sw_vers ProductName: macOS ProductVersion: 15.6 BuildVersion: 24G84 So I think that's the right KDK version for this system. I'm guessing the XCode version doesn't matter for these experiments (as long as the build succeeds), but for the record, I'm on XCode 16.4: xcodebuild -version Xcode 16.4 Build version 16F6 Apart from the other build instructions, the primary one I use to generate a DEVELOPMENT variant of the kernel is: export KDK=/Library/Developer/KDKs/KDK_15.6_24G84.kdk make SDKROOT=macosx KDKROOT=$KDK BUILD_WERROR=0 BUILD_JSON_COMPILATION_DATABASE=1 TARGET_CONFIGS=DEVELOPMENT ARM64 T6020 a
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’25
Crash in libquic.dylib when app is backgrounded and issues an HTTP/3 request on iOS 26
Title / Summary Crash in libquic.dylib when app is backgrounded and issues an HTTP/3 request Description On iOS 26, the app crashes inside libquic.dylib while performing a network request using HTTP/3 (QUIC) after the app has moved to the background. The crash happens within low-level QUIC / libquic internals. Reproduction Steps Launch the app, perform normal operations. Background the app (press home / switch away). While in background, trigger a network request that uses HTTP/3 / QUIC. Observe that the app crashes (stack trace pointing into libquic.dylib). Expected Behavior The HTTP/3 request in background should either be handled gracefully (fail or complete) without causing a crash; the app must not be terminated due to internal libquic failures. Actual Behavior The app crashes with signals/exceptions coming from libquic.dylib (in the QUIC / packet building / encryption / key state logic) when a HTTP/3 request is made in background. Environment / Device Information • OS: iOS 26 • Device: iPhone 1
3
0
128
Sep ’25
What is the difference between applying "hardened runtime" to an executable and adding the `-o library` flag to codesign?
Hey, Just recently I realized something I have been overlooking in my build pipelines. I thought that by adding the the hardened runtime, I disable 3rd-party library injection (I do not have the disable-library-validation entitlement added). However, I was using some checks on my code and I noticed that the library validation code signature check fails on my applications (e.g. adding the .libraryValidation requirement via the LightweightCodeRequirements framework) - with codesign -dvvvv /path/to/app I can check it doesn't have the CS_REQUIRE_LV flag: [...] CodeDirectory v=20500 size=937 flags=0x10000(runtime) hashes=18+7 location=embedded [...] then I used in Xcode the Other Code Signing Flags setting and added the -o library option, which added the flag: [...] CodeDirectory v=20500 size=937 flags=0x12000(library-validation,runtime) hashes=18+7 location=embedded [...] Is this flag something I should be explicitly setting? Because I was under the impression enabling hardened runtime would be enough. P
1
0
164
Sep ’25
Reply to Symbolicating kernel backtraces on Apple Silicon
I am unsure if there has been any progress in this area. But I needed to resolve a recent Tahoe panic, so chatgpt cobbled together this: https://gist.github.com/lundman/54e633a850e7623aae5adab38a39f464 If we are allowed to share? Either way, output was: ./symbolicate_panic.py -p ~/ZFS.2.3.1rc1.kernel.panic.-.Tahoe.M4.Pro.Mac.Mini.txt -k /Library/Extensions/zfs.kext/Contents/MacOS/zfs --kernel --kdk-nearest --accept-mismatch === KEXT mapping === bundle: org.openzfsonosx.zfs arch: arm64e base@: 0xfffffe004400d840 file __TEXT vmaddr: 0x0 file __TEXT_EXEC vmaddr: 0x70000 delta=0x70000 chosen TEXT_LOAD: 0xfffffe0043f9d840 === Kernel mapping (via KDK) === checking for KDK build 25A354 ... nearest: /Library/Developer/KDKs/KDK_26.0_25A353.kdk build: 25A354 SoC: t6041 kernel: /Library/Developer/KDKs/KDK_26.0_25A353.kdk/System/Library/Kernels/kernel.release.t6041 panic Kernel UUID: E67CAF31-8F84-389C-BB27-7FAEC762FA14 KDK Kernel UUID: E67CAF31-8F84-389C-BB27-7FAEC762FA14 file __TEXT vmaddr: 0xfffffe00
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’25
LibGDX/MobiVM App refuses to launch on iOS 26.0.1
Hello, currently I am having trouble releasing an app because it crashes/does not launch on iOS 26.0.1. We have uploaded apps in the past so I tried building one of them with our current toolchain. I use Xcode 16.4, Kotlin version 2.0.0, LibGDX 1.13.1 and robovm/MobiVM 2.3.23. I uploaded the build to TestFlight and tested with physical devices running iOS 18.5 and 26.0.1. It runs fine on 18.5 but refuses to launch on the 26.0.1 device. I cannot retrieve a crash log or .ips file because none is written. When I write a Console log while the app crashes/does not launch I get no hints as to why it does so. Do you maybe have additional ideas as to why it keeps not launching on iOS 26.0.1?
1
0
175
Sep ’25
Reply to LibGDX/MobiVM App refuses to launch on iOS 26.0.1
It’s hard to offer specific insight into this because I don’t maintain expertise in third-party tooling. I usually recommend that folks in your situation ask for help via the support channel for the tools they’re using. However, I can offer some general advice. My experience is that, when an app fails to launch like this, without generating a crash report, it’s usually because the third-party runtime has detected a problem and called exit. That’s fine during debugging, because you can get a breakpoint on exit and look at the backtrace. However, it’s problematic when the app is Distribution signed, because you can’t attach with the debugger. My usual advice here is to use Xcode to export a Development signed app from the same Xcode archive that you submitted to TestFlight. See Isolating Code Signing Problems from Build Problems. I’m not sure how well that’ll map to your third-party tooling. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple
Sep ’25
iOS 26 SwiftData crash does not happen in iOS 16
I have a simple app that makes an HTTPS call to gather some JSON which I then parse and add to my SwiftData database. The app then uses a simple @Query in a view to get the data into a list. on iOS 16 this works fine. No problems. But the same code on iOS 26 (targeting iOS 18.5) crashes after about 15 seconds of idle time after the list is populated. The error message is: Could not cast value of type '__NSCFNumber' (0x1f31ee568) to 'NSString' (0x1f31ec718). and occurs when trying to access ANY property of the list. I have a stripped down version of the app that shows the crash available. To replicate the issue: open the project in Xcode 26 target any iOS 26 device or simulator compile and run the project. after the list is displayed, wait about 15 seconds and the app crashes. It is also of note that if you try to run the app again, it will crash immediately, unless you delete the app from the device. Any help on this would be appreciated. Feedback number FB20295815 includes .zip file Below is the basic code (
4
0
174
Sep ’25
TestFlight iOS App Crashes on Distribution Build Created with Adobe Animate + AIR SDK
Hi After several successful development builds of my iOS app (built with Adobe Animate 24.0 Build 305 + AIR SDK 51.2.2.4), I moved to the distribution stage. The build was rejected by App Review due to crashing. To investigate, I uploaded the app to TestFlight and tested it myself. It immediately crashes on launch. To rule out my project code, I created a minimal build containing only one image (no code), but that also crashes in TestFlight. Development builds run fine on my device when using a development provisioning profile — the issue only occurs with TestFlight / distribution builds. Is there a way to identify the crash reason from Apple’s side? Or does iOS no longer support Animate / AIR SDK builds in distribution? I have crash logs (.ips) available and can share them if needed. Any guidance would be greatly appreciated. Thanks in advance.
1
0
59
Sep ’25
Reply to Metal 4 support in iOS simulator
Ah sorry for the lack of details, thanks for addressing this issue. Here's a swift code snippet to reproduce this issue: import MetalKit class MetalTestView: MTKView { var commandBuffer: MTL4CommandBuffer? var commandQueue: MTL4CommandQueue? } If you build with a real device selected, such as iPhone 14 with iOS 26 beta installed, the build succeeds, but if you build with iPhone 17 simulator with iOS 26, the build fails and complains that Cannot find type 'MTL4CommandBuffer/MTL4CommandQueue' in scope. Any way to get the simulator to recognize metal 4 types?
Topic: Graphics & Games SubTopic: Metal Tags:
Sep ’25
Can't install iOS 26.0 beta through xcodes or xcodebuild
I need to automate updating to latest iOS betas as part of my ci script, but I can't get it to install iOS 26.0 beta for the life of me, using xcodes or xcodebuild. I can see the version listed using xcodes runtimes --include-betas, and I tried sudo xcodes runtimes install iOS 26.0-beta1, but I would get the error Downloading Runtime iOS 26.0-beta1: 0% Error: ProcessExecutionError() I also tried xcodebuild -downloadPlatform iOS -buildVersion 23A5260l, where I found the specific build id on apples dev images website. But I would get the error iOS 23A5260l is not available for download. Specific version download failed, trying downloadPlatform ios latest... And similar error for trying xcodebuild -downloadPlatform iOS -buildVersion 26.0 or other version ids I found online. But this command would work for any other versions and betas listed on the website. I was able to install iOS 26.0 through xcodebuild -downloadPlatform iOS, which automatically installed it for me, but this is unideal for my situatio
4
0
250
Sep ’25