“translate scheme”

Sadly, I can’t read Chinese, so I’m answering based on a machine translation. The code you posted assumes that a specific interface type will have a specific interface name. That’s not a valid assumption. BSD interface names are not considered API on Apple platforms. I have a lot more information about this in the various posts referenced by Extra-ordinary Networking. Please read them through. If you have follow-up questions, I’d be happy to answer them here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

When you use SwiftData + CloudKit, under the hood, the SwiftData framework converts SwiftData models to Core Data managed objects, and use NSPersistentCloudKitContainer to synchronize the objects with CloudKit. NSPersistentCloudKitContainer mirrors each Core Data managed object to (at least) a CloudKit record (CKRecord), as described in Reading CloudKit Records for Core Data. To manage the internal state of the synchronization, it adds a few tables to the store, and the ANSCKRECORDMETADATA table is one of them, which is used to store the metadata of the CloudKit records. The metadata includes the system fields and encoded data of every CloudKit record, so yes, you can see that the size of table gets quite large. The ANSCKRECORDMETADATA table is an internal data structure that NSPersistentCloudKitContainer creates and consumes. You can review the documentation mentioned above to make sure that your models are translated to CloudKit schema correctly, but other than that, I don't see any way that can re

Here is a more step by step breakdown of the problem I have a iOS library that exposes a C function. This function is marked with default visibility and used via attribute tags to prevent the compiler/linker from stripping it #ifdef __cplusplus #define DYLIB_EXPORT extern C __attribute__((visibility(default))) __attribute__((used)) #else #define DYLIB_EXPORT __attribute__((visibility(default))) __attribute__((used)) #endif DYLIB_EXPORT bool say_hello_world(); #import helper_functions.h #import bool say_hello_world() { NSLog(@Hello WORLD 🟢!); return true; } From a dynamic library, called sdk, I want to call this function. In this example it's a Rust lib unsafe extern C { fn say_hello_world() -> bool; } #[unsafe(no_mangle)] extern C fn sdk_init() -> i32 { unsafe { say_hello_world(); } return 0; } When the app is compiled and launched from Xcode (either on debug or release schemes) then this works, the following snippet works and prints the hello WORLD message: #import OpacityObjCWrapper.h #impo

Hello yetanotherme, As per the discussion of preferredColorScheme(_:): If there are conflicting, non-nil color scheme preferences set by parallel branches of the view hierarchy, the system will prioritize the first non-nil preference based on the order of the views. Thus in your sample code, your initial preference set of .light should take precedence. When you swap lines 13 and 14, .dark sets both rectangles to be green, instead. Thank you for your patience, Richard Yeh ||  Developer Technical Support

I tried to disable swift-tasks-plugin-enabled as you described, but that barely had noticeable effect (<1s difference). With the debugger attached (and iPhone connected with USB) our app becomes responsive after about 6-7 seconds from start, while this time decreases to less than 1s if I turn off Debug executable option in scheme. I collected lldb-rpc-server sample as you described and added it to FB21378487. Hope it would be helpful!

Thanks for the post. Very interesting. My 5 cents if I may. It is crucial to prioritize user experience by ensuring consistency and stability in production environments. This is why feature flags, such as UIDesignRequiresCompatibility, are typically controlled by developers rather than end-users and are not exposed for arbitrary user-based toggling in production builds. This key allows developers to test the feature but does not provide a way to deploy it as it can be turned off, as explained in the documentation. Therefore, developers should refrain from rolling out new designs broadly before testing them thoroughly. Controlled feature flags enable developers to incrementally roll out new designs to ensure stability. By monitoring feedback and performance, developers can address issues before a full deployment. Apps submitted to the App Store should not contain hidden features or debugging options that alter the intended user experience for the general public. In development, set up different build schemes

👋Hi @DTS Engineer I remember that the form submitted last year needed to be filled in with Xcode or Playground test, and it seems that it was also mentioned: • If you use Xcode, the judges may use Simulator to run. • If you use Playground, it's a real machine. But my work this time will encounter two limitations: It will use the framework/API only available in iOS 26 (so if it is a Playground environment, it may not run) It will also use some content that must be real to run (such as ARKit), which means that Xcode Simulator is not good. So I would like to ask: Does this year's review allow you to compile and connect the iPad to the real machine? Or did I misremember last year's regulations? If the judge's environment is fixed (for example, only Playground or only Simulator), how should I adjust the submission method or implement the scheme? Looking forward to your reply, thank you. ~ Jiaxu Li

Tap Settings app > Developer > Sandbox Account to display a menu. Select and open Management from the menu, and you will see an option for Age Verification at the bottom of the screen. You can select a test case here. *This is an English translation from Japanese, so the wording may differ.

Same here. I created the new subscriptions during the recent App Store Connect problem, which was also acknowledged at https://developer.apple.com/system-status/. I encountered a lot of bugs when creating the new subscriptions, but somehow it saved them correctly anyway. I created three new subscriptions, and all have been approved and are ready to sell. However, only one of them is visible in the App Store, and only this one is purchasable by users. I'm pretty sure this is a bug because the subscription that users can purchase is visible on my app's detail page in the App Store, but with one important distinction: It only shows the English default translation, even though the German translation has been approved for my German App Store. This looks pretty broken... I would send you screenshots, but my App Store Connect is down again. 😃 I would be grateful if you could look into this @App Store Commerce Engineer Thanks a lot!

[quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] I already feel bad asking you again [/quote] No worries. It gives me a good excuse to brush up on my debugging skills (-: [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] It turns out that MTE and Malloc Stack Logging cannot be enabled at the same time. [/quote] Bah. This isn’t super surprising, and it’s the sort of thing I’d know if I had an iPhone 17 to play with. It’s definitely time to ping my boss about that. [quote='868455022, bims, /thread/806594?answerId=868455022#868455022, /profile/bims'] Unfortunately, I didn't really understand where/what to look for in Xcode. [/quote] OK. Lemme run you through a non-MTE example: Using Xcode 26.1 on macOS 15.7.1, I created an iOS app with two buttons wired up to these two methods: var memory: UnsafeMutableRawPointer? = nil func mallocAction() { self.memory = malloc(1024) } func freeAction() { free(self.memory) } In the scheme editor,