build disappears

The more obscure your app or system extension, the more important it is to lean into the system log. Logging to stdout is fine for simple things, but once you start building a complex product you usually run into some case where you can’t see such output. Moreover, you can never see such output once you ship your product, which makes it much harder to debug problems that only show up in the field. So, my advice here is that you use this as an opportunity to switch over to the system log. It’s easy to use, has many great features, and your log entries will be visible regardless of the context. See Your Friend the System Log for lots of hints and tips on this front. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’d like to clarify your overall goal here. Are you planning to ship an app based on Chromium? Or are you building some sort of plug-in that you install within Chromium? This matters because… [quote='800879021, poluyanov, /thread/800879, /profile/poluyanov'] simply overwriting files in the app bundle [/quote] Right. That breaks the seal on the code signature, which causes problems for all privacy subsystems, which rely on the code signature to track the identity of your code, that is, to determine that version N+1 of your app is the ‘same code’ as version N. This is something we call out in TN3179 Understanding local network privacy: To ensure that local network privacy reliably tracks the identity of your macOS program, sign it with an Apple-issued code-signing identity. Most apps don’t suffer from this problem because, when Xcode rebuilds the app, it signs result. If you’ve selected an Apple-issued code-signing identity, the new app has the same designated requirement as the previous app, and thus

@DTS Engineer What is your minimum deployment target set to? minimum deployment target set to 1 This is also an issue — that's a static library. .a files should never show up in a final app bundle, because their contents has been linked into some other binary during the build process. How can I integrate a static library (.a file) into an iOS app so that it does not appear in the final app bundle? Currently, I have defined a .podspec file and installed it via pod install.

What is your minimum deployment target set to? All of these libswift* files should no longer be included. They were necessary for compatibility purposes on iOS versions prior to Swift being built into iOS directly, which is long past now. 14221248 09-16-2025 10:33 Payload/Runner.app/Frameworks/libAudioFeature.a This is also an issue — that's a static library. .a files should never show up in a final app bundle, because their contents has been linked into some other binary during the build process. — Ed Ford,  DTS Engineer

I have previously referred to PTPPassThrough, but there is no example of sending the outData parameter, and I have not found it on Apple forums or online. So, I did find some test code of ours that does use outData. I can't directly provide the code, as it's part of a multi-layer architecture which means that code can't easily be provided. However, what I can say is: The way you've built out the structure generally appears correct. Every operation we send has type set to 1. It's actually hard coded into the method that builds out USB data packet. Nothing special is done to handle outData. The data object is built out as a separate data object and then included with the request. Finally, on the actual command you're sending, I don't know what the command format for 0x9205 actually is, but I don't think this is correct: unsigned char specialData = 1; NSData sendData = [NSData dataWithBytes:&specialData length:1]; As far as I can tell, the main reason the extra data approach is used is to provide a

tried to restore purchase Are you calling restoreCompletedTransactions() to restore your purchases? If yes, this method doesn't return in the following situations: All transactions are unfinished. The user did not purchase anything that is restorable. You tried to restore items that are not restorable, such as a non-renewing subscription or a consumable product. Your app’s build version does not meet the guidelines for the CFBundleVersion key.

@seanodonnell , @ToniMC Thank you for your Feedback reports. Please update your reports with a link to your failing build so our team can investigate the issue.

From restoreCompletedTransactions(): This method has no effect in the following situations: All transactions are unfinished. The user did not purchase anything that is restorable. You tried to restore items that are not restorable, such as a non-renewing subscription or a consumable product. Your app’s build version does not meet the guidelines for the CFBundleVersion key.

Does version mismatch affect already released builds? We have submitted an update using an Xcode RC build (17A321) after the keynote, the latest build number of Xcode is 17A324. I wonder if simply resubmitting will fix the crash.

Quinn asked me if I could take a look at this, and I have to say this is going to be a tricky one to track down. Let me start with the basics of what's going on. Pulling from your first crash log, here are the crucial details: Exception Type: EXC_BAD_ACCESS (SIGKILL) Exception Subtype: KERN_PROTECTION_FAILURE at 0x0000000000000000 Exception Codes: 0x0000000000000002, 0x0000000000000000 ... Termination Reason: CODESIGNING 2 Invalid Page ... Thread 4 name: Dispatch queue: assetsQueue Thread 4 Crashed: 0 ??? 0x0 ??? 1 Video Star 0x1012b34b0 __28-[ClipMixerView asyncRender]_block_invoke + 512 2 ...g_rt.asan_ios_dynamic.dylib 0x10559adf4 __wrap_dispatch_async_block_invoke + 196 3 libdispatch.dylib 0x19aacaaac _dispatch_call_block_and_release + 32 4 libdispatch.dylib 0x19aae4584 _dispatch_client_callout + 16 5 libdispatch.dylib 0x19aad32d0 _dispatch_lane_serial_drain + 740 6 libdispatch.dylib 0x19aad3dac _dispatch_lane_invoke + 388 7 libdispatch.dylib 0x19aade1dc _dispatch_root_queue_drain_deferred_wlh + 292 8 libd