Search results for

build disappears

49,456 results found

Post

Replies

Boosts

Views

Activity

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
Reply to Should UserSendCBD work on UAS interfaces?
I uploaded the requested IORegistryExplorer files. I also note a couple of other things: every time I re-attach the device, I get a new driver process and a new IOUserServer at the root of the IORegistry. Even if I delete the app the existing driver process keeps running, unless I kill it from Activity Monitor. Maybe there's something I'm not cleaning up properly, but I don't know what. when I eject the disk, there is a very perceptible delay between ejecting the volume and its associated - Data container. I use Finder/Settings and check the External Disks item in the Sidebar/Locations list. After I click the eject control next to the volume, I unplug the device as soon as it disappears from the sidebar, and very often see a notification about ejecting volume - data when it wasn't ready to be ejected. If I keep /Volumes open I can see that Volume's icon disappears first, then Volume - Data's icon. Is this a bug worth filing?
Topic: App & System Services SubTopic: Drivers Tags:
Sep ’25
Reply to Universal App on App-Store does not install on M3 MacBook Air
The issue was between my ears and not related to the app building or app store distribution. I did run the app locally from a ZIP (same for my friend with the M3 MacBook) and it had installed a bunch of settings under ~/Library and ~/Library/Preferences and this somehow conflicted with the App Store installation. I deleted all this and then could install from the App Store without issues. All good now, thanks! ER!K
Sep ’25
Reply to Building macOS apps with Xcode 26 on macOS 26 VM
Dual booting (triple in my case - 14/15/26) is not a viable option for Xcode development and testing of an app because different versions of macOS support different versions of Xcode. While Xcode 26.0.1 currently runs on macOS 26 and macOS 15.6, it certainly can't be run on macOS 14 and I can easily see a time in the near future where some version of Xcode 26.x requires macOS 26. Dual/triple booting does sound like a way to at least be able to run Test Flight so I can at least do my own verification of functionality before pushing the test build to beta testers. In my specific case, my app is not a game. It's a productivity app. My primary testing concern is ensuring the UI works correctly under different versions of macOS (and iOS for that matter). Being able to do this with VMs would make things SO much easier. One copy of Xcode on the host. One copy of the source code on the host. One build on the host. Then run that one binary (stored on the host) in the different VMs. It would be just l
Sep ’25
UIStepper can't reach min/max value
When I build my project with Xcode 26 the following code makes the stepper decrement option disabled: stepper.stepValue = 0.5 stepper.value = 1.0 stepper.minimumValue = 0.7 stepper.maximumValue = 4.0 I think the reason for this is that the (value - stepValue) goes bellow the minimumValue. But on all iOS versions before iOS 26 this made the decrement option enabled and it clamped the value to the minimumValue. The same issue can be reproduced for the maximumValue. Does anyone else have the same issue? Do we need to adjust the stepValue based on the current value?
1
0
76
Sep ’25
macOS 26 Launch Constraints
I've recently upgraded to the RC candidates of macOS 26 and Xcode 26. The app I'm building has a helper tool using SMAppService. When I run the app and helper tool in macOS 15 or macOS 26, all works as expected. When it runs on macOS 13 or 14, which previously worked. The helper now crashes on launch with the following reason: Termination Reason: CODESIGNING 4 Launch Constraint Violation I found this developer session which seems to address this, but the plist I've added doesn't seem to satisfy the constraint. https://developer.apple.com/videos/play/wwdc2023/10266/ Here are the contents of my new plist: Are there any gotchas here that I might be missing? Thanks!
12
0
1k
Sep ’25
SMAppService Sample Code seems broken
I abandoned Mac development back around 10.4 when I departed Apple and am playing catch-up, trying to figure out how to register a privileged helper tool that can execute commands as root in the new world order. I am developing on 13.1 and since some of these APIs debuted in 13, I'm wondering if that's ultimately the root of my problem. Starting off with the example code provided here: https://developer.apple.com/documentation/servicemanagement/updating-your-app-package-installer-to-use-the-new-service-management-api Following all build/run instructions in the README to the letter, I've not been successful in getting any part of it to work as documented. When I invoke the register command the test app briefly appears in System Settings for me to enable, but once I slide the switch over, it disappears. Subsequent attempts to invoke the register command are met only with the error message: `Unable to register Error Domain=SMAppServiceErrorDomain Code=1 Operation not permitted UserInfo={NSLocal
10
0
201
Sep ’25
Reply to Instructions for debugging recent macos kernel versions?
Short update - the linked article did help me successfully build a kext collection for the kernel on my local M2 system. I had to do minor adjustments to the instructions in that article to get it working. I have been trying to boot my M2 using this kext collection (after kmutil configure-boot ... successfully completed), but so far that step hasn't worked. Every time the system tries to boot with this custom built kext collection (in Permissive mode), the Apple icon shows up for a few seconds and then system shutdown and then again the Apple icon shows up and this keeps continuing. I switched back to Restrictive mode to allow me to boot the regular kernel, but I'll experiment some more and see how I can debug/investigate what's preventing a successful boot - it's going to be challenging because I can't seem to locate any logs for this part of the boot process.
Topic: App & System Services SubTopic: Core OS Tags:
Sep ’25