missing package product

We're building a VoIP app.When generating a VoIP certificate under Member Center > Certificates, Identifiers & Profiles > iOS Apps > Certificates > All > + (new) - there is no way to create Development (sandbox) VoIP certificate, only Production one.At the same time - Production VoIP certificate does NOT authenticate against production APNS (ssl://gateway.push.apple.com:2195). It only authenticates against the development APNS (ssl://gateway.sandbox.apple.com:2195).Is there a way to generate proper Development VoIP certificate?Is there a way to generate proper Production VoIP certificate that would authenticate against production APNS?Thank you.

Apple Transporter.app report this issue: Asset validation failed (90237) The product archive package's signature is invalid. Ensure that it is signed with your 3rd Party Mac Developer Installer certificate. In the post https://developer.apple.com/forums/thread/680438 Quinn “The Eskimo!” reply: For the Mac App Store you need: Apple Development: TTT (or the older Mac Developer: TTT) for day-to-day development 3rd Party Mac Developer Installer: TTT for signing the installer package you submit to App Store Connect 3rd Party Mac Developer Application: TTT for signing the code inside that installer package In https://stackoverflow.com/questions/29039462/which-certificate-should-i-use-to-sign-my-mac-os-x-application Apple Codesigning Certificate Types Mac App Distribution 3rd Party Mac Developer Application: Team Name Used to sign a Mac app before submitting it to the Mac App Store. Mac Installer Distribution 3rd Party Mac Developer Installer: Team Name Used to sign and submit a M

I have a code-signed app bundle that I need to convert to a *.pkg for submission (via Transporter) to the Mac App Store. This has worked fine in the past, but not after rebuilding the computer and recreating my certificates. (I had to downgrade to Catalina from Big Sur if that's relevant.) The command that fails is: $ sudo productbuild --component /Applications/Hollows.app --sign 3rd Party Mac Developer Installer: Gerald Schmidt (FBCSA85C72) hollows.pkg This leads to the error: productbuild: error: Cannot write product to hollows.pkg. (Could not find appropriate signing identity for “3rd Party Mac Developer Installer: Gerald Schmidt (FBCSA85C72)”.) According to Xcode and Keychain, this certificate is valid and the private key is present. However, if I validate it from the command line, I get: $ security find-identity -p macappstore ... 202B1775FC64882C215BCC8D52A2156038AEBD1C 3rd Party Mac Developer Installer: Gerald Schmidt (FBCSA85C72) (Missing required extension) Do I need to rec

Hi all I work in music production, the way the tools are set up is we use many tools (plugins) inside one larger app (a DAW), as such the process of setting up a machine to do work involves running 50-100+ different installers to get all tools installed. I'd like to write a small app that will automate the install process. I have a working approach for this where all steps work when run individually in terminal or via AppleScript, but as I create one unifying app I am running into an issue where any app I create in Xcode is not allowed to mount DMGs or give commands to terminal (even if I make a build app package and move it out of the Xcode directory, and even if I give explicit permission via settings) and if I try to have the app try to do the works via terminal it also can't seem to access terminal. I think there are some limitations I'm missing here. Any tips?

I have a swift Package, and I have some extra .h header to be shipped with the package, but this files are not copied to the build destination. It would be nice to have this files included as header in the modulemap file

The question about how to notarise an installer package (.pkg) containing a KEXT has come up on a number of threads [1] over the past few weeks. Unfortunately my answers have been less than clear, so I sat down with the notarisation team to fix that. The fundamental question here is the order in which you notarise things. Do you:Sign the KEXT, wrap the KEXT in a signed installer package, then notarise the package, then staple the ticket to the package (option A).Sign the KEXT, then notarise it, then staple the ticket to the KEXT, then wrap the KEXT in a signed installer package, then notarise the package, then staple the ticket to the package (option B).We generally recommend option A, because option B requires multiple round trips to the notarisation servers.For installer packages that don’t contain a KEXT, this is the end of the story. For installer packages that contain a KEXT, there is one extra gotcha. The gotcha, a

We provide our software on a single dmg that contains several pkgs that are then used individually on customer computers. That is, the installers will usually not be run directly from the dmg. So I think the correct approach is to notarize and staple each pkg before creating the dmg. In this case, is it unnecessary to notarize the dmg?And a similar question / request for clarification: I understand that notarizing a pkg will also notarize the apps contained therein, but is it the case that we only have to staple the pkg, and this will include whatever is needed for the apps as well?Thanks for any insights,Mark

I have an iOS app that includes a local Swift package. This Swift package contains some .plist files added as resources. The package also depends on an XCFramework. I want to read these .plist files from within the XCFramework. What I’d like to know is: Is this a common or recommended approach—having resources in a Swift package and accessing them from an XCFramework? Previously, I had the .plist files added directly to the main app target, and accessing them from the XCFramework felt straightforward. With the new setup, I’m trying to determine whether this method (placing resources in a Swift package and accessing them from an XCFramework) is considered good practice. For context: I am currently able to read the .plist files from the XCFramework by passing Bundle.module through one of the APIs exposed by the XCFramework.

Hello, I am currently learning SwiftUI through a paid course and am working on integrating Firebase into my project. While trying to add the Firebase package through Xcode, everything seems to work fine except for the fact that I am unable to find the FirebaseFirestoreSwift package. I am using the latest versions of both Xcode and macOS. I have attached a screenshot from the package manager where I couldn't locate the FirebaseFirestoreSwift package. Could you kindly assist me in resolving this issue? How can I correctly add this specific package to my project? Thank you for your support.

Hi everyone, I’m facing an issue where StoreKit is returning 0 products from the App Store, even though my auto-renewable subscriptions are approved in App Store Connect. When calling queryProductDetails using Flutter’s in_app_purchase package (which uses StoreKit under the hood), StoreKit reports success but returns an empty list. The logs show the following error: IAPError(code: storekit_no_response, source: app_store, message: StoreKit: Failed to get response from platform.) InAppPurchase.isAvailable() returns true, but no product details are received. Already verified: • Subscriptions are approved in App Store Connect • Product identifiers in the app match those in App Store Connect exactly • In-App Purchase capability is enabled in Xcode • Paid Applications Agreement, banking, and tax details are active and complete • Using the latest version of the Flutter in_app_purchase package StoreKit should normally return the list of available products in the production