xcode github

Output from my shell script that produces the application and the package installer: /Applications/com.gsequencer.GSequencer.app/Contents/MacOS/com.gsequencer.GSequencer.AudioUnitTest: replacing existing signature /Applications/com.gsequencer.GSequencer.app/Contents/MacOS/com.gsequencer.GSequencer.AudioUnitTest: signed Mach-O universal (x86_64 arm64) [com.gsequencer.GSequencer.AudioUnitTest] /Applications/com.gsequencer.GSequencer.app/Contents/MacOS/com.gsequencer.GSequencer: replacing existing signature /Applications/com.gsequencer.GSequencer.app/Contents/MacOS/com.gsequencer.GSequencer: signed app bundle with Mach-O universal (x86_64 arm64) [com.gsequencer.GSequencer] /Applications/com.gsequencer.GSequencer.app: replacing existing signature /Applications/com.gsequencer.GSequencer.app: signed app bundle with Mach-O universal (x86_64 arm64) [com.gsequencer.GSequencer] productbuild: Adding component at /Applications/com.gsequencer.GSequencer.app productbuild: Signing product with identity 3rd Party Mac Develop

@lionelng suggestion is spot on! I haven’t use subscription codes forever, however this usually points to an issue with how the products are set up in App Store Connect, or how they are being requested in your code. Go through Section 1 above meticulously. The Product ID exact match, Ready to Submit status, and complete metadata (localization, screenshot) are the most likely the issue? If you just created the IAPs, it can sometimes take a few hours for them to propagate through Apple's system. Do you have a test harness to request them? I believe, given your products not found error in Xcode, the problem is almost certainly in Section 1 (App Store Connect configuration) or Section 2 (Product IDs in code). The loading forever in production is a symptom of the app not being able to fetch the product details from the subscription? Provide here for other developer to help the response.invalidProductIdentifiers shows when you debug, and what the status of your IAPs is in App Store Connect. That will narro

Thank you for answering! In the meantime I tried another approach of creating the command line tools via SwiftPM and ran pretty much into the same issue here. The Package manifest defined two binaries with some dependencies and the build process again complained about multiple commands producing various frameworks. I fully agree that simplification is the way to go which is why the actual project has about 6 different frameworks into which the functionality is broken down. It is interesting to note that the error appears for frameworks that link external libraries - in one case it's swift-syntax and swift-system (as one of the libraries defines macros) and the other swift-subprocess. I wonder if this has any effect on this. When you have HelperTool and AdditionalHelperTool both linking MyFramework and both having an Embed Frameworks or Copy Files phase configured to copy MyFramework to Build/Products/Debug/Frameworks/, Xcode sees two distinct commands attempting to write to the identical location, le

@Noah______ Hey, I’m supportive of your idea to create an app about screen time! My app will also keep track of screen time in the background, but it will have a continuous counter timer that doesn’t need to be integrated with any frameworks. How did you put it together? Also, I sent an email to the Apple Swift student challenge email line and the WWDR (worldwide developer relations) told me that I need to ask companies like Nike Training Club and Headspace if it’s okay to use their videos and media locally in my Xcode assets. Is that true y’all?

Thanks for this very interesting issue that I’m sure many people has different ideas to deal with this reference to external projects. Will be great to see a simple focused project to see how you using it, when dealing with shared dynamic frameworks and multiple non-app targets like command-line tools. The error message Multiple commands produce... clearly indicates that two or more targets are trying to copy the same file In my personal experience, I address this challenge by consistently simplifying my projects to ensure that no project reference is duplicated and can be utilized throughout the entire project. While this approach may not be as straightforward as it appears, simplification has consistently proven to be my preferred solution when constructing projects. Xcode's build system, by default, tries to ensure that all linked dynamic frameworks are available. It is possible to reference a manager class once and utilize the accessed project instead of duplicating the framework. When you have H

If you are using SubscriptionStoreView with groupID overload, make sure the groupID entered is matching with the one in App Store Connect, not the one from your Xcode StoreKit configuration file. In Xcode testing, you need a StoreKit config file, and make sure to select Edit Scheme -> Options tab and select StoreKit Configuration to the correct configuration file. But this does not affect your App Store version. You might need to handle unfinished transactions. Take a look at sample code from WWDC25 on StoreKit 2.

[quote='872696022, joel2001k, /thread/812624?answerId=872696022#872696022, /profile/joel2001k'] As reading about Certificate types, I think this certificate is missing: [/quote] No. As I mentioned above, that platform specific distribution certificate type is no longer relevant. It’s been subsumed by Apple Distribution, which works for all platforms. [quote='872712022, joel2001k, /thread/812624?answerId=872712022#872712022, /profile/joel2001k'] What is with these 2 files? [/quote] You’re asking me?!? Seriously though, Apple’s standard processes don’t use openssl. If you go down that path, you won’t find any help from Apple sources. And I think that speaks to the main issue you’re having here: Apple’s code-signing infrastructure relies on digital identities in the keychain. A digital identity is the combination of a certificate and the private key that matches the public key in that certificate. Both of these have to be in the keychain. The openssl sequence you posted above doesn’t add the private key to the k

Added log files to FB20359822 (Packets and sample, with the experimental feature disabled and enabled) Xcode 26.2 in conjunction with iOS 26.2 fixed the exponential time it took to do a DLOpen with the debugger attached on Xcode 26, however the time it takes for one DLOpen is still ~0.10/0.15s on Xcode 26.x when it was only ~0.02/0.03s on Xcode 16.4. A huge number of DLOpens at app start will still cause the issue (We have around 200 dylibs that are loaded after app delegate init, mostly from Accessibility Bundles). 2000.15 = 30 seconds 2000.02 = 4 seconds Pretty consistent with what we see when the debugger is attached on Xcode 26.2 vs Xcode 16.4. Thank you. Sincerely, Marty, iOS @amo

If you’re just starting out I recommend that you allow Xcode’s automatic code signing to take care of your provisioning needs. That is: Launch Xcode. In Xcode > Settings > Apple Accounts, sign in with your developer Apple Account. Create a new project from the iOS > App template. In Signing & Capabilities, check “Automatically manage signing” and select your team in the Team popup. Attach your test device to your Mac via a USB cable. Build and run the test app on your device. Can you get that to work? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hi, Did you create a new CSR? Or re-submit an existing one? I run openssl and then on apple developer I have edited the certificate and submitted the new CSR. openssl genrsa -out ALDencryption.key 2048 openssl req -new -key ALDencryption.key -out csr2048ALDEncrypt.certSigningRequest -subj /emailAddress=****, CN=****, C=CH openssl genrsa -out ALDsigning.key 2048 openssl req -new -key ALDsigning.key -out csr2048ALDSigning.certSigningRequest -subj /emailAddress=****, CN=****, C=CH Then I downloaded the certificates and installed them. Provisioning profiles authorise, amongst other things, specific code-signing certificates. If you create a new certificate, you need to regenerate your profile. Xcode generates usually the embedded provisioning profile, but my Xcode setup isn't working. The archive action fails. I build from my makefile all dependencies so there are build directories for arm64, x86_64 and the final universal app build from make. I am unsure what Xcode actually does? Last