xcode github

Hi Quinn - we are using XCode's inbuilt toolchain. The constructor was called when we used the previous XCode toolchain, but is not called when built with XCode 16.4/26 toolchains. (Note that the comment facility here is failing to post comments, only replies)

[quote='808430021, wudiandy, /thread/808430, /profile/wudiandy'] does App Store Connect require the new build to originate from the same Xcode project … ? [/quote] No. [quote='808430021, wudiandy, /thread/808430, /profile/wudiandy'] does it only validate the Bundle Identifier and Version/Build Number? [/quote] Yes. Well, it validates a bunch of other stuff as well, but in terms of identifying your app that’s always done by its bundle ID. After that it runs a bunch of validation checks, one of which is to check the versions. Your proposed approach should work just fine; I’ve worked with many developers who’ve done this. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’d like to clarify your setup here. Are you using GCC proper? Or using the Clang that’s built in to Xcode with an attribute that just happened to originate in GCC? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi @DTS Engineer , Thank you very much for your responses, really helpful. For the past two weeks, I've been experimenting with a macOS System Extension application that manages three different Network Extension providers (NEFilterDataProvider, NETransparentProxyProvider, and NEDNSProxyProvider) housed within a single systemext bundle (Xcode target2), all managed and activated by a single main application(Xcode target1). My goal is to reliably capture comprehensive network activity logs from all three extensions simultaneously, particularly under high-traffic conditions. I've run into a few architectural questions regarding prioritization, concurrency, and logging reliability. Part 1: Extension Activation Order and Execution Predictability When multiple Network Extensions are active, how does the system process traffic, and is there a guaranteed order of execution? Q1: Given that all three extensions are active, is there a predictable order in which the network traffic will hit the providers

Given that you wrote “Created 6d” (6 days ago) and you paid successfully — you are probably still within a “normal but slow” window. I wouldn’t panic yet, but I’d allow maybe up to 7–10 business days. Waiting a bit more is reasonable. Meanwhile you can test your iPhone apps with just Xcode/Apple ID — but full distribution features rely on activation, which may take some days or require manual verification.

Where are you seeing this error? When you click Validate App in the Xcode organiser? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='808473021, raunits, /thread/808473, /profile/raunits'] we need to wrap them in a framework [/quote] Right. And there’s no built-in support for that. There are a couple of paths you might take here: Wrap it yourself. Use a mergeable library. The first option is obvious, but surprisingly tricky. You have to manually create a .framework wrapper around your dynamic library. The tricky part [1] is in crafting the correct Info.plist. I generally recommend that you create a test framework using Xcode and then crib the on-disk structure from that. Alternatively, you could update the build process for that “independent codebase” to create a mergeable library. You can then create a framework within your own app and merge that mergeable library into it. IMPORTANT Do this for each of the platforms you support, and remember that the device and the simulator are different platforms. Your best option here is to do it separately for each platform, and then merge it all together into one XCFramework. Finally,

You definitely want to use automatic code signing for this stuff (-: Try this: In Signing & Capabilities, enable automatic code signing on both targets. Then remove the App Groups capability from each target. Select a real device as a run destination and choose Product > Build. I’d expect that to work (-: Back in Signing & Capabilities, add the App Groups capability to the app target. And enable the relevant group from the list shown by that capability. Try building again. Repeat steps 4 through 6 for the widget target. How far do you get? And if things fail, what error do you see? Also, what version of Xcode are you using? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Try this: Using Xcode, create a new project from one of the iOS > App template. During the creation process, select your team, that is, the team that the app was transferred to. And enter the bundled ID of that transferred app. Build that for the device (so not the simulator). Does that work? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com